"The fire is out." Oh really?

[47Foxtrot]

I have the enemy point 99% capped, when a Myogi crosses the edge of it.  So I sink it.  Then a Kawachi comes in behind him.  He manages to hit me and set me on fire, but I sink him too.

 

I have 1,121 HP left and 32 seconds left on Damage Control cooldown.  Around the 4 second mark, I start mashing the R button.

 

With 10 HP left, the DC activates, and it says, "The fire is out."  Whew!

 

*BOOM*  Destroyed by the fire that is "out."

[J30_Reinhardt]

.....woulda lost by cap either way but yea that's a bit.... weird.

 

I think it has to do with the visual, text, and fire/smoke graphics pre-ceding the actual skill-timer.

As you can see in picture 1, there's still 3.5s left until its 'actually' out.

[Cruiser_Atago]

Yeah, happened to me numerous times.. A bit annoying since it elicits false hopes and then crushes them on the spot. 

[Blondie_the_Good]

Yeah, happened to me numerous times.. A bit annoying since it elicits false hopes then crushes them on the spot. 

 

This is exactly what I was thinking. +1

[Abyssal_Flagship]

Yeah, happened to me numerous times.. A bit annoying since it elicits false hopes then crushes them on the spot.

 

Welcome to Wargaming, enjoy your stay!

[Talleyrand]

I was there. 

[CHBanger]

Had the same happen to me. The fire burned out on its own, got the notification it was out, I had 100 to 200 hp left and a second later I died.

 

It's like it had one fire tick left to apply after it was out.

 

Very disappointing as I was in the middle of capping.

[teamoldmill]

Fire damage isn't real, according to WG and fans. Must have died from AP.

 

What others said, delay between message and actual extinguish. Could easily clean that up if they choose to.

[JRos83]

It's happened to me as well.

 

It's when the server flips its lid because you were not tagged to survive that match, so it says "screw you you're dying anyway."

[47Foxtrot]

Had the same happen to me. The fire burned out on its own, got the notification it was out, I had 100 to 200 hp left and a second later I died.

 

It's like it had one fire tick left to apply after it was out.

 

Now that's surprising.  I can understand a bug that displays the client-side notification before the DC process has finished--still a bug, mind you.  But for a fire that was extinguished on its own?  Wow...

 

Makes me wonder if there's an off-by-one error in the code somewhere that's applying an extra tick, like you said.

[Hualalai]

I had a wierd one recently.  Hit a ship, set him on fire.  He put the fire out.

 

A minute or two later, i get the message I sunk an enemy ship.  I did not shoot at him again.  And did not launch torpedoes.

 

In the after game report, it said I had started a fire,  but the fire did zero damage.

 

So I stole a kill from a team member with a fire that did zero damage,

[Sepplainr]

happens all the time. There is a tick of fire left after the verbal message is announced to you and the wheel completes. I don't like it but it's happened enough that I count on it.

[Suzunami]

I had a wierd one recently.  Hit a ship, set him on fire.  He put the fire out.

 

A minute or two later, i get the message I sunk an enemy ship.  I did not shoot at him again.  And did not launch torpedoes.

 

In the after game report, it said I had started a fire,  but the fire did zero damage.

 

So I stole a kill from a team member with a fire that did zero damage,

 

I got this quite a few times. I always thought it's my secondaries got lucky.

[SpiderWolve]

I have the enemy point 99% capped, when a Myogi crosses the edge of it.  So I sink it.  Then a Kawachi comes in behind him.  He manages to hit me and set me on fire, but I sink him too.

 

I have 1,121 HP left and 32 seconds left on Damage Control cooldown.  Around the 4 second mark, I start mashing the R button.

 

With 10 HP left, the DC activates, and it says, "The fire is out."  Whew!

 

*BOOM*  Destroyed by the fire that is "out."

Somebody didn't secure the fire hose.

[MajorRenegade]

Well this sound like we found a new bug for WG to fix. Hope they read this thread

[dahdah325]

There is a bit of a bug in the correlation between the time a consumable becomes available, the voice announcement of a consumable being used and the actual use. I see it regularly in a DD at the beginning of a match. If you are not careful, if you hit speedboost EXACTLY when the timer starts, the voice announcement comes up, but the SB does not activate. If you button mash right around the start point, you will often get 2-3 announcements overlapping each other in a weird echo-chamber effect. 

 

Actually, I thank you for mentioning this. I never remember to post a bug report, and now is a good time to do it. 

[QuicksilverJPR]

It does the same thing with flooding as well.  I got hit by a torp in my Atlanta just yesterday, which left me with approx 400hp because I immediately hit "R", and it fixed flooding, but then I died a second later to unknown cause.  I can only assume it's some kind of desync issue/delay issue.

[Striker_70]

This has happened to me a few times as well.  Hit the repair button before all the ship's hp is gone, but it still registers another tick of damage or two.

[Cragger]

There is a 1 tick delay for fires and flooding just like there is a delay for fires in WoT so that auto macros can't be used to negate all dot damage.