Because with that low proc chance it is unlikely that you will actually land a killing hit on someone while his shields are still up (or get him even close to 0 before stripping shields).
So in the end you still have to destroy the shields and then the hull and depending on how the proc works (50% bypass shields or 50% in addition to the full shield damage) normal Tetryons might even be better at the first.
It's both procs. so you get the standard 2.5% shield drain, and a 2.5% to have 50% of your attack bypass shields and cause hull damage.
2 procs are better than one.
Now obviously for pure damage and critical chances there will be better weapons and your correct that you most likely won't land a killing hit, and yes it won't do any shield damage, but it's still an extra proc.
I'll be honest though i probably won't be trading my fleet weapons for them anytime soon, but hopefully they'll add fleet versions of the hybrid/experimental weapons.
Any reason why cannon builds are favored in this case? You can get dual cannons and turrets and DBB if you don't use a torpedo.... Now i fly a Recluse, the weapons seemed intresting till i realized there are no BEAMS, so what i'll put some random tetryon in the back and 3 DBBs upfront?
Put a standard beam array as reward too please!
Something about it being usable with the Harpeng, I guess the DOT on them were different damage types and could be stacked, Bort didn't really say more than they don't want both on the same ship, and since KDf Roms could easily get both, they decided to remove it.
How difficult is it to make it so it can't be mounted on the same ship? It seems like it would be a pretty simple bit of coding.
If Hargh'peng present then No to Radiant
If Radiant present then No to Hargh'peng
I'm not even a programmer, but it looks like it would take just two if then statements in the code used to process the mounting (via drag and drop) of weapons. The present variable wouldn't even need to be added to the game because there is already a number present limitation on certain torpedoes (limit 1) like the Hargh'peng.
In fact, the same code used to limit the number of Hargh'peng torps to one could be used to block the Radiant. It would be simply treated as a second Hargh'peng by the system and blocked by the existing code. All that would take then, is to slightly expand the existing blocking code to include the Radiant. Then, the regular code that limits the number of mounted Hargh'pengs would also limit the number of Radiants to one.
Last edited by mercuriciodide; 12-05-2013 at 11:44 AM.