Secondary Battery HE Detonations. Is it supposed to be 100%

[Xanthro]

Two more detonations today. I can't manage 10 games without a detonation, and even 5 games is hard.

Both times today, the detonation were caused by secondary battery HE from a German BB. You might want to check the code on that. In many cases, the first secondary battery HE that lands I'm getting detonated.

I had around 19 detonations in 2,600 games, including ranked games.

I've had 13 in the last 130 games.

Something has to be wrong in the code. Nobody should be getting detonated as often as I'm experiencing.

[bad_arcade_kitty]

the nature of random is streaky

well you know that stuff - an evil chance seldom comes alone, it never rains it pours etc

 

also mm1 mod and use those flags

[1nv4d3rZ1m]

I detonated three ships a in three games a couple days ago. One was a Fletcher I detonated in my roon, with secondaries. The damage report said 1 secondary shell did 6k damage. 

 

I am running det flags on all my DDs because I fear the retribution of RNG. 

[RipNuN2]

Random detonations are random so your numbers arent unexpected. You can always mount the module or flags to reduce or eliminate them.

[Xanthro]

Random detonations are random so your numbers arent unexpected. You can always mount the module or flags to reduce or eliminate them.

 

Module is mounted. Flags need to be saved for ranked.

And yes, the numbers I'm seeing are not to be expected. If something has a 1/100 chance of happening, and you see it happen 13 times in 130. It's unlikely it's simply a random streak.

[bad_arcade_kitty]

i recall a game that i had a while ago when i literally detonated two dd in a row with two shells from my dd, 1 shell - 1 detonation, second shell - second detonation

 

they accused me of hacking btw

[RivertheRoyal]

 

Module is mounted. Flags need to be saved for ranked.

And yes, the numbers I'm seeing are not to be expected. If something has a 1/100 chance of happening, and you see it happen 13 times in 130. It's unlikely it's simply a random streak.

 

Random means that you can detonate 30 times in a row, and then never see a detonation again. It's random. Literally anything could happen.

[Valas1]

Two more detonations today. I can't manage 10 games without a detonation, and even 5 games is hard.

Both times today, the detonation were caused by secondary battery HE from a German BB. You might want to check the code on that. In many cases, the first secondary battery HE that lands I'm getting detonated.

I had around 19 detonations in 2,600 games, including ranked games.

I've had 13 in the last 130 games.

Something has to be wrong in the code. Nobody should be getting detonated as often as I'm experiencing.

 

You weren't by chance playing a detonation prone ship, like an Omaha were you?

[Xanthro]

Random means that you can detonate 30 times in a row, and then never see a detonation again. It's random. Literally anything could happen.

 

Tell you want, roll a 100 sided dice and have it come up with 100, and do that 30 times in a row. It will never happen.

What can happen in theory doesn't mean you will ever experience it in your lifetime. You'll never ever experience an random 1 in a Nonillion event caused by you.

[Xanthro]

 

You weren't by chance playing a detonation prone ship, like an Omaha were you?

 

I wouldn't know, because I don't know what ships are more prone to detonation. I've played hundreds of matches in DDs and never experienced anywhere near as many detonations, and I'd think each DD is about the same in terms of detonations.

[_Sarcasticat_]

 

Random means that you can detonate 30 times in a row, and then never see a detonation again. It's random. Literally anything could happen.

 

 

You weren't by chance playing a detonation prone ship, like an Omaha were you?

Coupled with ships with thin armor and detonation-prone, like Omaha or Benson/Fletcher, there's a large chance he'll get detonated. Even then, as River has stated, it's all quite random. 

[CylonRed]

I am not detonating anyone in my Gneis or Bismark with the secondaries so it is no where near 100% like the title states...  If you are going to play a detonation prone class and not run flags.......  then you are going to get detonated.

[Skpstr]

What can happen in theory doesn't mean you will ever experience it in your lifetime.

 

Doesn't mean it won't either.

[Xanthro]

Of course, first game today, German BB Secondary HE shell detonation, 22K health. Just gone. There is obviously a bug. The first salvo of German Secondary HE that has landed has detonated me at a 100% rate, and it's happened for well over a hundred games and many days. It's making the game unplayable, since I can't come anywhere near a German BB without just instant dying. 1, just 1, that's right ONE Secondary HE shell lands, I'm detonated. And this isn't the only time. Literally, if a German BB Secondary HE Salvo lands, I detonate. The only time it records more than one secondary HE shell lands is if more than one shell in the hitting salvo lands.

This simply cannot be intended. And no, nobody is that unlucky.

[McDoob]

I have a great solution.

 

If secondaries are ripping you apart, DON'T GET INTO SECONDARY RANGE!

 

Your main complaint is against German BBs, the same ships which are known to have the best secondaries in the game. If you're taking your ship that close to them, you have no reason to expect anything different.

 

I wholly understand your frustration about detonations. I've created a thread about it before, too. It's a pain in the rear, but it's in the game, and unlikely to get removed. Deal with it. And don't forget, you get ten anti-detonation flags when you get detonated. Might want to, I don't know, use them?

[Xanthro]

First game today. Detonation.

It simply cannot be intended that a detonation happens every single day, and happens once every 10 games.

[CylonRed]

First game today. Detonation.

It simply cannot be intended that a detonation happens every single day, and happens once every 10 games.

 

nad yet - it is only you. Sorry - WG has not in any way picked you out as special to detonate no matter what...

[Xanthro]

 

nad yet - it is only you. Sorry - WG has not in any way picked you out as special to detonate no matter what...

 

From a programming perspective, there are only two choices available.

1. Exceedingly bad streak of luck.

2. Something in programming specific to my ship, modules and choices that is increasing the percentage chance of a detonation.

 

Once 1 because exceedingly unlikely, which it already has, 2 becomes more and more likely.

Obviously, there is no programming specific to my name that is in the game. That doesn't mean there isn't an error in the code that is affecting me and increasing the rate of detonations beyond what is expected.

 

No person over many games should be experiencing anything near a 1 in 10 detonation rate. That's just simply way too high.

Again, I've in DDs I've had a detonation rate of 1/100 and now it's 1/10. That's not normal.

[CaptGodzillaPig]

First game today. Detonation.

It simply cannot be intended that a detonation happens every single day, and happens once every 10 games.

 

  Are you actually getting "detonation" or are you just getting wiped out with one salvo in a devastating strike?   If this was a code issue or a game problem then it would be happening to everyone and it seems that you are either the unluckiest guy alive or something is a happening in the game that isn't being fully explained here.

 

Based on your theory of this being a "code" issue I should be det'ing DD's at least every other game with my GK as I usually have a chance to get decent number of second hits on no less than 2 DD's per game.   I did get a Dev Strike on a DD yesterday with my seconds, but that wasn't a det.

[CylonRed]

 

From a programming perspective, there are only two choices available.

1. Exceedingly bad streak of luck.

2. Something in programming specific to my ship, modules and choices that is increasing the percentage chance of a detonation.

 

Once 1 because exceedingly unlikely, which it already has, 2 becomes more and more likely.

Obviously, there is no programming specific to my name that is in the game. That doesn't mean there isn't an error in the code that is affecting me and increasing the rate of detonations beyond what is expected.

 

No person over many games should be experiencing anything near a 1 in 10 detonation rate. That's just simply way too high.

Again, I've in DDs I've had a detonation rate of 1/100 and now it's 1/10. That's not normal.

 

#1 far, far, far more likely than #2 and have no idea what the following means "Once 1 because exceedingly unlikely, which it already has". 

 

The chances of others running your set up is actually not bad and hence - if #2 was the issue then more people would be having it.

[Raptor_alcor]

even if it's just 1% it's possible for it to happen repeatedly, this is a fact of life. THe odds of being struck by lightning are extremely low yet someone had it happen to them 7 times. 

[Xanthro]

And another detonation. Not even ten games yet and 2 detonations. 

Keep pretending that there isn't an issue or bug.

[Xanthro]

Ten games today, 2 detonations. 2 Yesterday, 2 the day before that, and 2 the day before that. But this is normal.

At least, make it so you get flags on every detonation, as opposed to only the first.

[Fiona_Marshe]

DDs do have a tendancy to explode when a HE shell slides under the stern quarter. The explosion radius slaps the magazine hit box (where a BB HE shell immediately hits the max 10% det chance due to mechanics.)

 

Had a string a while ago, exact same situation each time. Turning away from contact, the shell landed in the water behind the stern, sliding underneath whers there is no armour protection. A HE shell that actually strikes the DD deck doesn't reach the magazine hit box due to armour.

[Taregant]

Curious I also detonated a minotaur this time with Yammy secondaries and it was also literally the first shell...