Vicious death is bugged, its not just an UI error, wake up zos.

olsborg · May 2016

Another one of these threads, I know there are plenty others, but ZOS is doing a fine job ignoring this issue so here goes.

I know its not an UI error because I see the explosion happen at 20% hp and then I take the killing hit.

DjKahun · May 2016

I can confirm that it's not a UI bug too! As I was by myself. Someone also uploaded a video on YouTube to prove it! FIX IT ZOS every single set you release to this game is bloody broken!

Sharee · May 2016

olsborg wrote: »

I know its not an UI error because I see the explosion happen at 20% hp and then I take the killing hit.

You see the explosion happen at 20% HP because that's what you HP was at when you got hit by the killing blow (radiant destruction tick, in this case)

Think of the VD explosion as a proc attached to any damaging hit that carries enough damage to kill you. It's animation plays at the same time as the animation of the killing blow.

From another thread:

Sunburnt_Penguin wrote: »

So I've just watched a video of me last night where I seemingly exploded with ~30% health remaining.

I've just used the combat text to work it out (health - damage + healing) and the animation and damage showed up before I was actually at zero health but just after the final blow came which killed me.

I don't believe it's bugged.

Chain of events for anyone interested. Arsed uploading a video and all that.

Look at the table. The explosion animation plays immediately as you get hit by the last hit that killed you, not after your health bar decreased to zero after the last hit.

You have 8K life left, you get hit by 8K damage hit, you immediately see the VD explosion(at the same time the hit connects), then you see your health bar decrease to zero and you fall over.

Sunburnt_Penguin · May 2016

OP what was your health? Your delta was 19k damage taken without VD damage and 26k with it.

Also, there's obviously damage (and possibly healing) that isn't showing on the recap due to there being a Lotus Fan tick. Even if your health was greater than 19k, this literally proves nothing.

NovaShadow · May 2016

If it really is a UI bug. All ZOS needs to do is fix the UI bug and then we'll see what happens.

I don't believe its a UI bug.

daswahnsinn · May 2016

daswahnsinn wrote: »

Just some death recaps, I'm not saying it's bugged or what not, but it procs often. The last one is the same player hitting me.

FatKidHatchets · May 2016

Its ui error.

Tested it myself.

You see yours on your death recap, but it did no damage to you.

kinggingernator · May 2016

Literally what you said doesn't change anything. The explosion doesn't actually do damage early, and it's simple to test. Stand there in front of someone who hits hard w/ viscous death, don't heal or shield, and let them blow you up in less than 5 abilities. Viscous death will show up along with the 4 abilities he used, and if you add them up it's clear the viscous didn't proc and you would have died without it.

Duiwel · May 2016

Can confirm it's UI we tested it out also by stopping the fight at less than 5% and no explosion happened.

daswahnsinn · May 2016

Like I said, I'm not saying it's not UI, but why would the same player have it proc ever other hit? I don't care the set exist in it current state, more just wondering.

As a side note, I had to remove the names per TOS. Other than that, no proof.

Alcast · May 2016

HEALTH DESYNC usually. That is how I get killed by VD boyz. 50% Hp thinking I am fine bam RIP 1 Light attack.

idk · May 2016

daswahnsinn wrote: »

Like I said, I'm not saying it's not UI, but why would the same player have it proc ever other hit? I don't care the set exist in it current state, more just wondering.

As a side note, I had to remove the names per TOS. Other than that, no proof.

It appears your concern has been answered by multiple sources explaining that from their tests VD isn't hitting ge target before death.

It probably shows up in our death recaps and add-ons since it occurs at the very moment we die from other means.

rfennell_ESO · May 2016

Regardless of whether VD is bugged or not...

The combat log is rarely in order. By that I mean it often is out of order of actual attacks and is unreliable.

Lenikus · May 2016

I tested it myself many times.
The UI error is real, however, sometimes, you DO get hit by it.
i've been hit with it on a dk flight thingie and did not die because i had shields (harness magicka) up.
can't prove it but you can test it with well-calculated damage and that DK flight ulti since it's physical dmg

Necrelios · May 2016

They could just remove the fifth set bonus and replace it with something less provocative I suppose. The problem with these discussions is that you only have half the story, what you see on your end and what information your client reads and in what order could be a lot different than what the server sees and processes. Due to lag, some information can be sent in the wrong order, and the third party tools along with the death recap are just displaying the order the information was sent to them, not necessarily the order it actually happened.

rfennell_ESO · May 2016

What they should have done and probably should do is make vicious death a delayed proc. 1 second, 2 seconds maybe 3 seconds.

As it is, well it doesn't really stop zerging (as intended) and is just a burden in game.

InvitationNotFound · May 2016

olsborg wrote: »

I know its not an UI error because I see the explosion happen at 20% hp and then I take the killing hit.

Already did some testing as others did as well. It wasn't possible to reproduce it. Anyway, i don't say it isn't buggy... but instead "i know its..." you could try to reproduce it or provide some evidence. An no, the screenshot isn't evidence at all as the order is usually a mess and VB appears before the last hit, even if it's not the case.

DjKahun wrote: »

I can confirm that it's not a UI bug too! As I was by myself. Someone also uploaded a video on YouTube to prove it! FIX IT ZOS every single set you release to this game is bloody broken!

The video provided, if we're talking about the same, was worthless as it started in the middle without a proper log. Again, I'm not claiming it isn't bugged, but there hasn't been proper evidence yet... only a lot of QQ (and yes, it's a band-aid fix as a lot of other "fixes" are. but that's another subject.).