Funny Fails & Epic Plays - World of Warships Speshul Compilation - Episode 47 

i was not sure what killed that smolensk - but your comment made it clear... 7:41 helps to find

Exposure to the JINGLES-21 virus tends to result in serious difficulties recognising common objects. Sadly both Flamu and Flambass have fallen to the condition.

To be fair Bourgogne player is one of the best players on EU server

Bourgogne is a Unicum, no idea what he did there

@@theinstinctsven guess he had to poop and went full yolo to at least make some damage 😁

same

check stats, unicum/super unicum player ... how??? (The Rammer=

Or you kill someone full hp in one salvo and don't get it - _-

wow, lagged dev strike

Yeah that’s what’s been happening to me. Slapped a Schcors in my Georgia for 25k, then overpenned him on the final blow and got a devstrike.

@@Virgilfinnatell I got both de strike and arsonist with the same kill in thunderer lol

@@Martel_Clips I didn’t think it worked on fires. Ofc it was Thunderer. That ship deserves to be removed completely from the game.

Probably of all time!

Dev strikes are bugged right now.. I've gotten dev strikes on ships I never fired at all game until near the end.. only had 2k health.. I've also legit done what should be dev strikes to ships and got nothing.

The time span is only a few seconds between salvos (so a ripple fire would still count, as would firing guns and torps, and fast reloading ships can sneak one in with two salvos). But as BirdForce said, they've been completely bugged for at least the last four patches, where things that don't meet all (or sometimes even any) of the criteria will sometimes give a dev strike, and things that meet all of the criteria sometimes won't.

The enemy ship was about to die anyway, the ram was a waste. (in my humble noob-like opinion)

Or the total amount within a set short period of time?

@@laszlokaestner5766 Don't know ... I managed to potato a torp dodge at the beginning of a game and suffered the final 700 damage from the same guy like 10-12 mins later. The guy won the devastating strike medal.

With the number of reports I've seen of it being awarded with completely different conditions, it's very unlikely, and almost guaranteed a bug. It's still 50%+ to an enemy ship with a single salvo (or multiple if they're close enough together to be within the few second window) and kill it, which has been confirmed by WG in one of the early bug report posts four months ago when this issue first showed up. But people will get the achievement for multiple salvos well outside that window (I got one off a Colbert in my Thunderer where it took two salvos 20 seconds apart to kill and still triggered), sometimes it won't trigger when every single condition is met, and then sometimes it will work correctly.

@@MidnightPhoenix07 now as you mention... I was happily derping around in a Hipper, exchanging unfriendly shots with an Alaska, when I got rudely interrupted by a Yamato. 4 or 5 hits on me, all 32K hp deleted on the spot from like 18-20 km and the Yamato did not get a medal.

I guess Roon didn't like him and dumped him to the curbside??

yep, if kills happen at once. also new bugged devastating strike which requires to deal % of hp no matter how many volleys you send

Yep, there's a short window where subsequent kills can still count. The most I've seen personally is three in a single match (BB kills a cruiser with guns and then immediately rams an enemy BB), and once I saw a screenshot and replay of _four_ first bloods in a single game. But typically the most you'll see is two, either in the case of mutually assured torpage between two DDs or two ships ramming right at the start.

same

No they didn't change the criteria, the achievement has just been bugged for the last four patches. Sometimes it will work correctly, sometimes you'll get a dev strike without fulfilling all (or even any) of the criteria, and sometimes you'll meet every requirement and still not get it. About a month ago, I got a dev strike off a Colbert in my Thunderer with two salvos (the first took him from 100% to around 10-15%, and then the next finished him off 20 seconds later, well outside the multiple salvo window), and then a few battles after I nuked a Neptune in my Vladivostok (100-0 in one salvo) and didn't get it. A day or so after that, I killed a Sinop in my Vladivostok that was around 70% in one salvo, and got it. It's been reported on reddit and the forums since the first day of the patch, with tons of replays submitted, and it still hasn't been fixed or even really acknowledged beyond the initial 'we'll look into it.' Then again, the main battery reload bug was investigated and supposedly fixed in the current patch according to the bug fix list, and it still pops up every now and then.

Actually, he knows. The achievement is buggy as hell though... it shows up when the condition is not even met.

Yeah the achievement is currently bugged right now.