Team damage system broken in 0.6.10

[Hades_warrior]

As you all are familiar with TK status', we can assume that this system is buged (as one of many other bug's in latest patch).

Here's why;

Im playing KGV, and I wanted to kill Shimakaze on close range my broadside, so in same time Shima fired his torpedos in 45° direction to catch Colorado from my team who was slightly ahead of me, I hit Shima and kill him but one of my HE shells (ONE) stuck to Colorado and I got TK status.

Colorado eat at least 3-4 Shima torp's which caused flooding to him, and I got TK with damage penalty of 40,000 damage. I mean, what the hell... Shima's flooding was caused to Colorado AND me. I got hit by only 1 torpedo from Shima, and my HP droped from full to low in just few seconds. And 1 torpedo cant cause me 40,000 damage.

My hit on Shima was double kill for me (red ribbons x2), and battle ended with 3 kills for me. Very strange battle.

I know KGV is OP ship, but one shell cant cause 40,000 damage, especially not to BB...
I know I could submit bug report on WG's support page but im sure it wont help in my situation.

 

btw, one of my friends from clan who was in division with me was recording, so i'll try to upload replay of that battle.

[Commander_Cornflakes]

Waiting for the Replay.

[mtm78]

At least it sounds pretty funky, and OP didn't contain any whining so I guess it looks like a legit issue. That said ->

11 minutes ago, Commander_Cornflakes said:

Waiting for the Replay.

[Commander_Cornflakes]

Btw. do you have screenshots of the after battle reports?

[Hades_warrior]

4 minutes ago, Commander_Cornflakes said:

Btw. do you have screenshots of the after battle reports?

Not anymore. I exit game few battles later as we finished for today. But I see your point and now I regret I dont have it :/

Ill try to get that replay tomorrow when clan mate comes online. I dont have it exept he told me he did record.

[ColonelPete]

Have you seen what type of damage you did?

Maybe you caused a fire?

[Hades_warrior]

1 hour ago, ColonelPete said:

Have you seen what type of damage you did?

Maybe you caused a fire?

Seems it was caused fire from my HE shell, which caused TK for me, but in the same moment he got hit by 3-4 Shima's torpedos which caused flooding but also I got lower HP like I got hit from those 3-4 torpedos. Exept only 1 torp hit me.

We all know how this latest patch is full of bugs, so no wonder if system like TK is bugged too...

[ColonelPete]

When the fire damage sank him, you got the TK status.

It was bad luck that the fire damage made the last tick to sink him and not the flooding.

But that is no bug.

[MudMonkey]

Well well well, first things first. For me it looks like that you and the Colorado were together in a division. Not that it is important in this case of TK. But you wrote that you were facing a Shima. KGV and Colorado are tier 7, so I guess your 3rd division member was at least a tier 8. Don't do that. To bring two tier 7 into a tier 10 game is kinda unfair towards your team members. And tier 8 are facing a LOT of tier 10 battles.

 

Now them rulez.

Let me quote here:

"Has done 10,000 or more damage to allies in the most recent 1,000,000 main battery damage (1% of the damage to allies)"

" Killing an ally with main battery, torpedoes, or aircraft"

 

So either way you have caused quite some tk-damage in your previous games or you killed your division mate with that fire. That is why you are pink.

 

As good ol' Pete said, it is not a bug but the system working as intended.

[SteDorff]

I also thought I had seen a bug  because there was no penalty whatsoever I saw a t9 BB do damage to a friendly cruiser both in smoke then a cruiser who hit torpedo's in a friendly BB then a BB who killed a friendly cruiser and thus ending the battle in a loss.

 

After waching the replay I saw the t9BB s secundairies banged the shots into the friendly cruiser causing no damage. the cruiser that got shot at by the friendly BB would have been killed by that shot BUT the replay showed an enemy shot from the other side that sunk the cruiser split second before the friendly BB pumped his salvo in. The only team damage thus caused where the torpedo's from a cruiser into a BB but one of 3 torpedo's hit a sunken ship so only 2 of his torpedo's hit a friendly and they did low damage.

 

A fine mess that battle was.  but it showed that it all happened differently then it looked at first and was no bug.

[Hades_warrior]

10 hours ago, ColonelPete said:

When the fire damage sank him, you got the TK status.

It was bad luck that the fire damage made the last tick to sink him and not the flooding.

But that is no bug.

No, it was not the last tick. If I did the last tick then it would be -1 kill for me, but I end up round with 3 kills in total.

 

6 hours ago, MudMonkey said:

Well well well, first things first. For me it looks like that you and the Colorado were together in a division. Not that it is important in this case of TK. But you wrote that you were facing a Shima. KGV and Colorado are tier 7, so I guess your 3rd division member was at least a tier 8. Don't do that. To bring two tier 7 into a tier 10 game is kinda unfair towards your team members. And tier 8 are facing a LOT of tier 10 battles.

 

So either way you have caused quite some tk-damage in your previous games or you killed your division mate with that fire. That is why you are pink.

 

Well it looks wrong to you, because Colorado was not in division with me. I was with two clan mates in division. One was DD and other was cruiser if I remember right and all 3 of us was 7's. So there was no mixing of 7-8 tier MM. But I did see lot of other divisions 7-8 lately.

Its possible I miss-saw the name of enemy DD for other kaze, Kamikaze who is tier 5 and offen in t7 MM.

 

Usualy I dont fire at my allies. Only red messages I see in chat are when someone run into me (blind sailors). I see to many of those.

The cause of that Colorado's death and ofc big amount of damage was from 3-4 DD torpedos he got hit and flooded.

[Shirakami_Kon]

1 hour ago, Hades_warrior said:

Colorado was not in division with me. I was with two clan mates in division. One was DD and other was cruiser if I remember right and all 3 of us was 7's.

 

Then I'd worry more about a MM bug than the teamkill bug if it's such a thing in this case. Because you can't face a Shimakaze with a whole T7 division. T7 doesn't meet T10, ever.

[ColonelPete]

2 hours ago, Hades_warrior said:

No, it was not the last tick. If I did the last tick then it would be -1 kill for me, but I end up round with 3 kills in total.

 

Well it looks wrong to you, because Colorado was not in division with me. I was with two clan mates in division. One was DD and other was cruiser if I remember right and all 3 of us was 7's. So there was no mixing of 7-8 tier MM. But I did see lot of other divisions 7-8 lately.

Its possible I miss-saw the name of enemy DD for other kaze, Kamikaze who is tier 5 and offen in t7 MM.

 

Usualy I dont fire at my allies. Only red messages I see in chat are when someone run into me (blind sailors). I see to many of those.

The cause of that Colorado's death and ofc big amount of damage was from 3-4 DD torpedos he got hit and flooded.

then the fire burned very long

without result screens, we can only speculate

[Juanx]

You would think, someone as outraged as to come to the forum to moan, would have taken screenies.

Im calling shenanigans on this one.

[ForlornSailor]

I dont know guys. This is the third time im reading something like this in the forums the last days. Maybe there is a bug out there? Plz get the replay up @Hades_warrior. Also, screenshots would be very helpfull from final result, but if u dont have them...

 

One Post i did find, the other I dont know where I read it. But afaik it involved a RN BB also...

 

On 6.9.2017 at 11:54 PM, pzkpfwv1d said:

It also appears that WG have done something to the disciplinary penalty.  Firing at another BB from Iron Duke, shots were hitting the enemy BB but I ended up with a teamkill penalty.  Appeal and asked for replay videos, however, nobody will explain how to get a replay videos in the WG staff

 

That guy has nearly 7k games played so I think he´d notice if he fkked up or his secondaries would be to blame?

[Juanx]

15 minutes ago, ForlornSailor said:

I dont know guys. This is the third time im reading something like this in the forums the last days. Maybe there is a bug out there? Plz get the replay up @Hades_warrior. Also, screenshots would be very helpfull from final result, but if u dont have them...

 

One Post i did find, the other I dont know where I read it. But afaik it involved a RN BB also...

 

 

That guy has nearly 7k games played so I think he´d notice if he fkked up or his secondaries would be to blame?

 

Secondaries were long ago removed from team damage, imagine being near a german T7+ BB while it peppers a DD with secondaries, half the team would get on fire from secondaries.

[MudMonkey]

6 hours ago, Hades_warrior said:

No, it was not the last tick. If I did the last tick then it would be -1 kill for me, but I end up round with 3 kills in total.

 

Well it looks wrong to you, because Colorado was not in division with me. I was with two clan mates in division. One was DD and other was cruiser if I remember right and all 3 of us was 7's. So there was no mixing of 7-8 tier MM. But I did see lot of other divisions 7-8 lately.

Its possible I miss-saw the name of enemy DD for other kaze, Kamikaze who is tier 5 and offen in t7 MM.

 

Usualy I dont fire at my allies. Only red messages I see in chat are when someone run into me (blind sailors). I see to many of those.

The cause of that Colorado's death and ofc big amount of damage was from 3-4 DD torpedos he got hit and flooded.

 

Yes, it looks wrong. And not only to me I guess. I also guess that you remember incorrectly. So far I have never heard of such things like getting into tier 10 battles with a 3 x tier 7 division. And if you are incorrect with that then you might also be incorrect with other things.

 

I don't like to quote and therefore repeat myself. I stand to what I have said earlier with what I have quoted about how you get pink. And I still strongly believe that it was one of the two possibilities. I don't believe that the TK system is buggy. We would have heard of it way more.

[SteDorff]

I did just have a mach in a Friedrich in where 2 members of a clan in my team decided to sink my ship one Moskva who did 2046 and 2046 and 696 damage and a Khabarovsk doing  627 and 5016 turned around and sent me 5 of his torpedo's but since I was engaging the enemy on cap I was backing up and only 2/5 hit me but did damage of 8679.

 

Now I did see the Moskva getting pink and he got the damage reversed to him like it supposed to is however the Khabarovsk did not turn pink only the message in chat and did not receive reversed damage he did 14322 damage total that is more then the Moskva shouldn't he have had the pink status and reversed damage upon him as well?

[Commander_Cornflakes]

7 minutes ago, SteDorff said:

I did just have a mach in a Friedrich in where 2 members of a clan in my team decided to sink my ship one Moskva who did 2046 and 2046 and 696 damage and a Khabarovsk doing  627 and 5016 turned around and sent me 5 of his torpedo's but since I was engaging the enemy on cap I was backing up and only 2/5 hit me but did damage of 8679.

 

Now I did see the Moskva getting pink and he got the damage reversed to him like it supposed to is however the Khabarovsk did not turn pink only the message in chat and did not receive reversed damage he did 14322 damage total that is more then the Moskva shouldn't he have had the pink status and reversed damage upon him as well?

Since they didn't kill you, it's about the team damage they did in this game and the games before.

• Has done 10,000 or more damage to allies in the most recent 1,000,000 main battery damage (1% of the damage to allies) 
• Has done 10,000 or more damage to allies in the most recent 1,000,000 aerial bomb damage (1% of the damage to allies) 
• Has done 10,000 or more damage to allies in the most recent 1,000,000 aerial torpedo damage (1% of the damage to allies)
• Has done 40,000 or more damage to allies in the most recent 1,000,000 torpedo damage, was done to the allies (4% of the damage to allies) 

[SteDorff]

Well 5643 HE damage and 8679 torpedo doesn't it add? There is also a difference in accidental and purpose this was obviously purpose

[Commander_Cornflakes]

10 minutes ago, SteDorff said:

There is also a difference in accidental and purpose this was obviously purpose

There is not, it's the all the same for the TK-System. Because how should it decide which was accidental and which was on purpose?

[Hades_warrior]

8 hours ago, ForlornSailor said:

I dont know guys. This is the third time im reading something like this in the forums the last days. Maybe there is a bug out there? Plz get the replay up @Hades_warrior. Also, screenshots would be very helpfull from final result, but if u dont have them...

 

What do you mean about bug? Is it really a 3rd time this type of thread lately? That should be considered as real problem than.

 

5 hours ago, MudMonkey said:

I don't believe that the TK system is buggy. We would have heard of it way more.

You haven't see any of bugs in this latest patch? Many of us faced them and why is hard to believe that even TK system is broken.

I saw numerous, and besides this another one (which I found very annoying) was broken healing. I was in Queen Elizabeth at the time and when I hit heal, it showed like it heals full HP. Not only normal amount recovery but full HP (green indicator), but of course it didnt.

 

Anyway, clan friend send me the replay today, here is the replay. I dont know if these replay have spectator features, otherwise its impossible to see closer what and how happen. I didnt see the cause on act, only the result (when camera transfer to my ship).

And my bad. It wasn't Colorado on DD torpedo but Nagato (dont know why I taught it was Colorado), not Shima (as it was Shiratsuyu)...

Friend in Mahan, other mate in Pensacola and me KGV. It was 12 min into battle, when I got double strike.

 

20170908_215210_PASD006-Mahan-1936_41_Conquest.wowsreplay

[Commander_Cornflakes]

3 minutes ago, Hades_warrior said:

What do you mean about bug? Is it really a 3rd time this type of thread lately? That should be considered as real problem than.

Not really, there are dozens of "CV OP", "Tirpitz got ninjanerfed" and "AIMBOT!1!!" threads without any of them being true

 

4 minutes ago, Hades_warrior said:

20170908_215210_PASD006-Mahan-1936_41_Conquest.wowsreplay

Can you tell us the timestamp when we have to look closely please?

[Hades_warrior]

Just now, Commander_Cornflakes said:

Not really, there are dozens of "CV OP", "Tirpitz got ninjanerfed" and "AIMBOT!1!!" threads without any of them being true

 

Can you tell us the timestamp when we have to look closely please?

12 min into battle. So -8 remaining.

I edited post.

[Commander_Cornflakes]

Alright, I know what happened.

 

First: Please tell your friend to use camouflages on his DDs :P

 

Second: Everything is working as intended.

 

You hit the Nagato with one shell on his superstructure. RNG hated you and made this one shell start a fire on the Nagato (he even said that later in chat).

That fire burned for a few ticks, until the damage from it was enough to make you pink. Then he burned for a few more ticks and because you were pink, the damage got reflected to you and multiplied as punishment.

Now we have roughly an estimated 5k fire until you got pink, another 5k fire afterwards and 30k reflected damage on yourself, adding up to those 40k total team damage. (Yes, the reflected damage on your own ship does count for your team damage.)

 

That's it. No bug visible ^^