VISCIOUS DEATH- 100% confirmed broken on PS4

Crom_CCCXVI

First- I play on PS4. I don’t claim to know what happens on PC or Xbox platforms, so if you don’t play on PS4- please don’t act like you about my platform..

Second, I didn’t save a screenshot, I wish I would have. I was more questioning to my group that VD was proc’d by a siege than going off early. It seems most PVPers I run with already operate on the fact BVD proc’s early to the point even some Stamina builds wear the set. The only place it seems to be debated anymore is in these forums.
I am on Scourge and Blackwater quite a bit with Cravility, Mourningstar, Raiders of Cyrodil under the same screen name, so maybe someone will recognize my name and vouch I’m not just some troll- or making up a lie like I was accused of in another thread.

Thirdly, three of my characters are currently wearing VD, I paid a bit for the jewelry parts, so I don’t hate the set.

But this is real simple:
Saturday night in Scourge , red and yellow fighting over Blue Road almost all night, at one point I sneak down to Sejanus by myself helping to flag it quick and cut off their lines.
I don’t see any counter attack so I put up 3 stone trebs..

Then blam DEAD.

- A cold fire ballista hit me from the roof for over 16K. Huge hit.
- Viscious Death goes off for another 8K
That is the entire death screen. Two things. No "out of order", no "UI error".... just a huge hit from a ballista, VD and death.

My health was right around 23K. (it may have been lower, I'm not sure if I had the bar with Entropy on it, or which armor set was fully activated depending on which weapons/shield I had up at the time.

So stop debating whether it procs early or not, it’s totally clear. I use the set, it is what it is…..but please stop all the misinformation.

leepalmer95

Crom_CCCXVI wrote: »

First- I play on PS4. I don’t claim to know what happens on PC or Xbox platforms, so if you don’t play on PS4- please don’t act like you about my platform..

Second, I didn’t save a screenshot, I wish I would have. I was more questioning to my group that VD was proc’d by a siege than going off early. It seems most PVPers I run with already operate on the fact BVD proc’s early to the point even some Stamina builds wear the set. The only place it seems to be debated anymore is in these forums.
I am on Scourge and Blackwater quite a bit with Cravility, Mourningstar, Raiders of Cyrodil under the same screen name, so maybe someone will recognize my name and vouch I’m not just some troll- or making up a lie like I was accused of in another thread.

Thirdly, three of my characters are currently wearing VD, I paid a bit for the jewelry parts, so I don’t hate the set.

But this is real simple:
Saturday night in Scourge , red and yellow fighting over Blue Road almost all night, at one point I sneak down to Sejanus by myself helping to flag it quick and cut off their lines.
I don’t see any counter attack so I put up 3 stone trebs..

Then blam DEAD.

- A cold fire ballista hit me from the roof for over 16K. Huge hit.
- Viscious Death goes off for another 8K
That is the entire death screen. Two things. No "out of order", no "UI error".... just a huge hit from a ballista, VD and death.

My health was right around 23K. (it may have been lower, I'm not sure if I had the bar with Entropy on it, or which armor set was fully activated depending on which weapons/shield I had up at the time.

So stop debating whether it procs early or not, it’s totally clear. I use the set, it is what it is…..but please stop all the misinformation.

Go google more threads.

1. It does not proc early it's been tested by people on pc with add ons, videos, people count the dmg. The only reason it appears on your recap is an UI error that zos have confirmed.
2. The reason you died may be have from 2 ticks of the siege, it may have been because you were dmg or the likely cause was that you was hp desync, so despite looking like you was full hp you was actually around the 16k mark and died.

You yourself is only adding to the misinformation .

Leandor

leepalmer95 wrote: »

Crom_CCCXVI wrote: »

First- I play on PS4. I don’t claim to know what happens on PC or Xbox platforms, so if you don’t play on PS4- please don’t act like you about my platform..

Second, I didn’t save a screenshot, I wish I would have. I was more questioning to my group that VD was proc’d by a siege than going off early. It seems most PVPers I run with already operate on the fact BVD proc’s early to the point even some Stamina builds wear the set. The only place it seems to be debated anymore is in these forums.
I am on Scourge and Blackwater quite a bit with Cravility, Mourningstar, Raiders of Cyrodil under the same screen name, so maybe someone will recognize my name and vouch I’m not just some troll- or making up a lie like I was accused of in another thread.

Thirdly, three of my characters are currently wearing VD, I paid a bit for the jewelry parts, so I don’t hate the set.

But this is real simple:
Saturday night in Scourge , red and yellow fighting over Blue Road almost all night, at one point I sneak down to Sejanus by myself helping to flag it quick and cut off their lines.
I don’t see any counter attack so I put up 3 stone trebs..

Then blam DEAD.

- A cold fire ballista hit me from the roof for over 16K. Huge hit.
- Viscious Death goes off for another 8K
That is the entire death screen. Two things. No "out of order", no "UI error".... just a huge hit from a ballista, VD and death.

My health was right around 23K. (it may have been lower, I'm not sure if I had the bar with Entropy on it, or which armor set was fully activated depending on which weapons/shield I had up at the time.

So stop debating whether it procs early or not, it’s totally clear. I use the set, it is what it is…..but please stop all the misinformation.

Go google more threads.

1. It does not proc early it's been tested by people on pc with add ons, videos, people count the dmg. The only reason it appears on your recap is an UI error that zos have confirmed.
2. The reason you died may be have from 2 ticks of the siege, it may have been because you were dmg or the likely cause was that you was hp desync, so despite looking like you was full hp you was actually around the 16k mark and died.

You yourself is only adding to the misinformation .

Lol.

Sunburnt_Penguin

"100% confirmed broken" yet only provides details of events: no screenshots or vid.

As @leepalmer95 said, there may be other reasons why you died. An obvious one is that there could've easily been someone else in close proximity who died and you didn't see due to not paying attention. Without a video to analyse after the event, you can't be 100% certain.

I am also on PS4 and have recorded ~5 of my deaths where I thought "okay, the 'VD bug' killed me". However, after watching over the videos and doing the step-by-step calcs which occurred, I have found that it's working as intended in every situation.

95% of people who claim it's bugged fall in to the category of "I saw me die n itz bugged plz fix", whereas the other 5% post some sort of video of VD procing before death without a full chain of events and log to actually determine if it did.

Next time you die from a suspected 'VD bug' simply open the combat log and record the last 15 minutes of gameplay. Look around to make sure that no one died close to you and if not, then using your starting health, minus each damage taken (excluding the VD proc) and plus each healing received in sequence. If you have health remaining before the VD damage is added then it's bugged. However, if not then it's working as intended.

That is how you actually determine if it's "100% confirmed broken".

Armitas

His health is 23k. If he died there should be at least 23k damage in his death log regardless of whether the siege ticked twice or if his health was desynced. Are there any other explanations to account for the missing 7k damage that vicious death is now conveniently filling?

I know people tested it but they can only test under the conditions they know of. For example what if his health is desynced and the proc is triggering off the desynced health rather then the real health?

Nilmot

Relying on death log for accurate information is a fools errand.

Sunburnt_Penguin

Armitas wrote: »

His health is 23k. If he died there should be at least 23k damage in his death log regardless of whether the siege ticked twice or if his health was desynced. Are there any other explanations to account for the missing 7k damage that vicious death is now conveniently filling?

I know people tested it but they can only test under the conditions they know of. For example what if his health is desynced and the proc is triggering off the desynced health rather then the real health?

@Armitas
Well, OP says his/her health was ~23k but may've been lower because he/she wasn't sure if it was on his Entropy bar. If he/she wasn't, then it would've been 8% less at ~21k. It's entirely possible that he/she wasn't aware that food (if he/she runs it) ran out thus reducing health by at least ~5k, leaving him/her with ~16k.

That 16k does actually tie-in with the Ballista damage.

Rohamad_Ali

Sunburnt_Penguin wrote: »

"100% confirmed broken" yet only provides details of events: no screenshots or vid.

As @leepalmer95 said, there may be other reasons why you died. An obvious one is that there could've easily been someone else in close proximity who died and you didn't see due to not paying attention. Without a video to analyse after the event, you can't be 100% certain.

I am also on PS4 and have recorded ~5 of my deaths where I thought "okay, the 'VD bug' killed me". However, after watching over the videos and doing the step-by-step calcs which occurred, I have found that it's working as intended in every situation.

95% of people who claim it's bugged fall in to the category of "I saw me die n itz bugged plz fix", whereas the other 5% post some sort of video of VD procing before death without a full chain of events and log to actually determine if it did.

Next time you die from a suspected 'VD bug' simply open the combat log and record the last 15 minutes of gameplay. Look around to make sure that no one died close to you and if not, then using your starting health, minus each damage taken (excluding the VD proc) and plus each healing received in sequence. If you have health remaining before the VD damage is added then it's bugged. However, if not then it's working as intended.

That is how you actually determine if it's "100% confirmed broken".

Don't drag logic into this

Sunburnt_Penguin

Roehamad_Ali wrote: »

Sunburnt_Penguin wrote: »

"100% confirmed broken" yet only provides details of events: no screenshots or vid.

As @leepalmer95 said, there may be other reasons why you died. An obvious one is that there could've easily been someone else in close proximity who died and you didn't see due to not paying attention. Without a video to analyse after the event, you can't be 100% certain.

I am also on PS4 and have recorded ~5 of my deaths where I thought "okay, the 'VD bug' killed me". However, after watching over the videos and doing the step-by-step calcs which occurred, I have found that it's working as intended in every situation.

95% of people who claim it's bugged fall in to the category of "I saw me die n itz bugged plz fix", whereas the other 5% post some sort of video of VD procing before death without a full chain of events and log to actually determine if it did.

Next time you die from a suspected 'VD bug' simply open the combat log and record the last 15 minutes of gameplay. Look around to make sure that no one died close to you and if not, then using your starting health, minus each damage taken (excluding the VD proc) and plus each healing received in sequence. If you have health remaining before the VD damage is added then it's bugged. However, if not then it's working as intended.

That is how you actually determine if it's "100% confirmed broken".

Don't drag logic into this

Bby pls stahp.

Bfish22090

leepalmer95 wrote: »

Crom_CCCXVI wrote: »

First- I play on PS4. I don’t claim to know what happens on PC or Xbox platforms, so if you don’t play on PS4- please don’t act like you about my platform..

Second, I didn’t save a screenshot, I wish I would have. I was more questioning to my group that VD was proc’d by a siege than going off early. It seems most PVPers I run with already operate on the fact BVD proc’s early to the point even some Stamina builds wear the set. The only place it seems to be debated anymore is in these forums.
I am on Scourge and Blackwater quite a bit with Cravility, Mourningstar, Raiders of Cyrodil under the same screen name, so maybe someone will recognize my name and vouch I’m not just some troll- or making up a lie like I was accused of in another thread.

Thirdly, three of my characters are currently wearing VD, I paid a bit for the jewelry parts, so I don’t hate the set.

But this is real simple:
Saturday night in Scourge , red and yellow fighting over Blue Road almost all night, at one point I sneak down to Sejanus by myself helping to flag it quick and cut off their lines.
I don’t see any counter attack so I put up 3 stone trebs..

Then blam DEAD.

- A cold fire ballista hit me from the roof for over 16K. Huge hit.
- Viscious Death goes off for another 8K
That is the entire death screen. Two things. No "out of order", no "UI error".... just a huge hit from a ballista, VD and death.

My health was right around 23K. (it may have been lower, I'm not sure if I had the bar with Entropy on it, or which armor set was fully activated depending on which weapons/shield I had up at the time.

So stop debating whether it procs early or not, it’s totally clear. I use the set, it is what it is…..but please stop all the misinformation.

Go google more threads.

1. It does not proc early it's been tested by people on pc with add ons, videos, people count the dmg. The only reason it appears on your recap is an UI error that zos have confirmed.
2. The reason you died may be have from 2 ticks of the siege, it may have been because you were dmg or the likely cause was that you was hp desync, so despite looking like you was full hp you was actually around the 16k mark and died.

You yourself is only adding to the misinformation .

I have seen it proc early in large scale keep fights with bad latency, frames and alot of sieve/abilities going off

Rohamad_Ali

The problem on ps4 is there are no add ons to help read the damage and crunch the numbers , like on PC , to see if it's a desynchronized calculation on the health bar . Thus showing the animation apparently early because you were already going to die . Also the death recap on all systems is bugged .

Sunburnt_Penguin

Roehamad_Ali wrote: »

The problem on ps4 is there are no add ons to help read the damage and crunch the numbers , like on PC , to see if it's a desynchronized calculation on the health bar . Thus showing the animation apparently early because you were already going to die . Also the death recap on all systems is bugged .

As I said above, recording the last 15 minutes and analysing the starting health - damage taken + healing received from the combat text is all that's needed to see if any damage from VD comes in to play.

It's so easy to do that I'd have expected some of those pro-VD-bug to provide their evidence through this, however, I haven't seen a single one

Armitas

Sunburnt_Penguin wrote: »

Armitas wrote: »

His health is 23k. If he died there should be at least 23k damage in his death log regardless of whether the siege ticked twice or if his health was desynced. Are there any other explanations to account for the missing 7k damage that vicious death is now conveniently filling?

I know people tested it but they can only test under the conditions they know of. For example what if his health is desynced and the proc is triggering off the desynced health rather then the real health?

@Armitas
Well, OP says his/her health was ~23k but may've been lower because he/she wasn't sure if it was on his Entropy bar. If he/she wasn't, then it would've been 8% less at ~21k. It's entirely possible that he/she wasn't aware that food (if he/she runs it) ran out thus reducing health by at least ~5k, leaving him/her with ~16k.

That 16k does actually tie-in with the Ballista damage.

It's possible, but it does require more assumptions than the OPs conclusion. Not that Occam's Razer points to the truth, just that the OPs conclusion is still ahead as one of the properly preferable explanations.

Rohamad_Ali

Sunburnt_Penguin wrote: »

Roehamad_Ali wrote: »

The problem on ps4 is there are no add ons to help read the damage and crunch the numbers , like on PC , to see if it's a desynchronized calculation on the health bar . Thus showing the animation apparently early because you were already going to die . Also the death recap on all systems is bugged .

As I said above, recording the last 15 minutes and analysing the starting health - damage taken + healing received from the combat text is all that's needed to see if any damage from VD comes in to play.

It's so easy to do that I'd have expected some of those pro-VD-bug to provide their evidence through this, however, I haven't seen a single one

I thought I did a week ago but then math happened ....

Sunburnt_Penguin

Armitas wrote: »

Sunburnt_Penguin wrote: »

Armitas wrote: »

His health is 23k. If he died there should be at least 23k damage in his death log regardless of whether the siege ticked twice or if his health was desynced. Are there any other explanations to account for the missing 7k damage that vicious death is now conveniently filling?

I know people tested it but they can only test under the conditions they know of. For example what if his health is desynced and the proc is triggering off the desynced health rather then the real health?

@Armitas
Well, OP says his/her health was ~23k but may've been lower because he/she wasn't sure if it was on his Entropy bar. If he/she wasn't, then it would've been 8% less at ~21k. It's entirely possible that he/she wasn't aware that food (if he/she runs it) ran out thus reducing health by at least ~5k, leaving him/her with ~16k.

That 16k does actually tie-in with the Ballista damage.

It's possible, but it does require more assumptions than the OPs conclusion. Not that Occam's Razer points to the truth, just that the OPs conclusion is still ahead as one of the properly preferable explanations.

Well you did ask for explanations to account for the missing health and I see that as a viable one, not an unnecessary one. Especially given as how Entropy would've been on OP's offensive bar, not the buff-bar which - if OP is sieging correctly - would've been the bar OP would be on.

I see that explanation as a lot more preferable to account for a missing 7k health than due to a bug which I haven't found - through analysis of similar situations as OP described - to exist.

Sunburnt_Penguin

Roehamad_Ali wrote: »

Sunburnt_Penguin wrote: »

Roehamad_Ali wrote: »

The problem on ps4 is there are no add ons to help read the damage and crunch the numbers , like on PC , to see if it's a desynchronized calculation on the health bar . Thus showing the animation apparently early because you were already going to die . Also the death recap on all systems is bugged .

As I said above, recording the last 15 minutes and analysing the starting health - damage taken + healing received from the combat text is all that's needed to see if any damage from VD comes in to play.

It's so easy to do that I'd have expected some of those pro-VD-bug to provide their evidence through this, however, I haven't seen a single one

I thought I did a week ago but then math happened ....

Damn math, ruining conspiracies.

FatKidHatchets

I play ps4.
I use the set.
It doesn't proc early.

Indeed stop the misinformation.

Armitas

Sunburnt_Penguin wrote: »

Armitas wrote: »

Sunburnt_Penguin wrote: »

Armitas wrote: »

His health is 23k. If he died there should be at least 23k damage in his death log regardless of whether the siege ticked twice or if his health was desynced. Are there any other explanations to account for the missing 7k damage that vicious death is now conveniently filling?

I know people tested it but they can only test under the conditions they know of. For example what if his health is desynced and the proc is triggering off the desynced health rather then the real health?

@Armitas
Well, OP says his/her health was ~23k but may've been lower because he/she wasn't sure if it was on his Entropy bar. If he/she wasn't, then it would've been 8% less at ~21k. It's entirely possible that he/she wasn't aware that food (if he/she runs it) ran out thus reducing health by at least ~5k, leaving him/her with ~16k.

That 16k does actually tie-in with the Ballista damage.

It's possible, but it does require more assumptions than the OPs conclusion. Not that Occam's Razer points to the truth, just that the OPs conclusion is still ahead as one of the properly preferable explanations.

Well you did ask for explanations to account for the missing health and I see that as a viable one, not an unnecessary one. Especially given as how Entropy would've been on OP's offensive bar, not the buff-bar which - if OP is sieging correctly - would've been the bar OP would be on.

I see that explanation as a lot more preferable to account for a missing 7k health than due to a bug which I haven't found - through analysis of similar situations as OP described - to exist.

It is a viable explanation I agree.

DHale

I rolled an alt just to test. I play on pc not bugged at all. The reason you think it's bugged is lag and the already confirmed visual bug combat log tell you your dead then a vd proc it bumps the fifth or last part of your death recap not the one ability that actually killed you. In lag it appears no one is near then latency hits and some whom that died near you blows apart killing you. The server catches up. This is no different than the crit Rush wrecking blow from ppl you never even saw. Then you pan your camera through the the blue haze to find.... No one. Vd the only thing I can safely say is working as intended.

Sunburnt_Penguin

Armitas wrote: »

Sunburnt_Penguin wrote: »

Armitas wrote: »

Sunburnt_Penguin wrote: »

Armitas wrote: »

His health is 23k. If he died there should be at least 23k damage in his death log regardless of whether the siege ticked twice or if his health was desynced. Are there any other explanations to account for the missing 7k damage that vicious death is now conveniently filling?

I know people tested it but they can only test under the conditions they know of. For example what if his health is desynced and the proc is triggering off the desynced health rather then the real health?

@Armitas
Well, OP says his/her health was ~23k but may've been lower because he/she wasn't sure if it was on his Entropy bar. If he/she wasn't, then it would've been 8% less at ~21k. It's entirely possible that he/she wasn't aware that food (if he/she runs it) ran out thus reducing health by at least ~5k, leaving him/her with ~16k.

That 16k does actually tie-in with the Ballista damage.

It's possible, but it does require more assumptions than the OPs conclusion. Not that Occam's Razer points to the truth, just that the OPs conclusion is still ahead as one of the properly preferable explanations.

Well you did ask for explanations to account for the missing health and I see that as a viable one, not an unnecessary one. Especially given as how Entropy would've been on OP's offensive bar, not the buff-bar which - if OP is sieging correctly - would've been the bar OP would be on.

I see that explanation as a lot more preferable to account for a missing 7k health than due to a bug which I haven't found - through analysis of similar situations as OP described - to exist.

It is a viable explanation I agree.

I would post the videos that I analysed as I imagine they show the exact situations that a lot of people experience when claiming it's bugged, however:
1. I can't be arsed
2. My YouTube account is a personal one
3. My PSN is unique and the same as my social media handles
4. It contains PSNs of friends who may not be happy with it going up
5. Me showing that it's not bugged is not indisputable evidence of it not being bugged

In saying point 5, I'm going to keep believing that it's not bugged due to absence of evidence. Surely at least one person who claims it to be bugged would have been able to post indisputable evidence rather than the half-baked videos that have been put up?

Zaldan

there are way too many bugs that need fixing in this game to state anything with any kind of certainty lets face it

Crom_CCCXVI

OK Here is the Deal..
- I came to these forums because I was trying to find out whether Viscious Death was proc'ing from "burn damage" being applied by 1 player, if the kill stroke came from another, like many people believe it is. Then I see people in this forum still debating something that was settled long ago.

---

The hardcore PvP guys, the ones that play 50-60+ hours a week, the ones that hold emperor time and time again, don't play in forums much. In fact, I might be the only person in any of the guilds I know who ever comes to forums.
- It is common knowledge VD procs early in PvP on PS4. Join a PvP guild, a serious one. and start telling them you did a "test". You have guys that die 200X a night, they don't do test.----

I was killed by a single Ballista Bolt, in single combat which proc'd VD. there was no lag, I was by myself. there was no other damage from somewhere else.... clear as day. How many of you even knew siege weapons were proc'ing VD? Maybe someone should go run some "tests" on that?

The only person lying is the guy who said he "rolled an alt". Got him to L10, went into Cyrodil and "ran a test" withing 5 hours of me making my last post, LOL... yeah right, sure you did.



You guys keep trusting in the forum, but if your ever in Scourge on a Friday/Saturday playing EP, look me up. I play by the same name. I'll introduce you to 50 guys who play like the game is a full time job (some I don't even know where they get the time) and you can tell these guys who die a few hundred times a week each, that you ran a test on a forum. -- Maybe after running a full group for a few hours, getting enough PvP experience you'll see a long with a couple other bugs "that don't exist" according to ZOS. The only way your going to find this out is by extensive play, not two or three attempts to see something in a controlled environment.

Sunburnt_Penguin

Crom_CCCXVI wrote: »

OK Here is the Deal..
- I came to these forums because I was trying to find out whether Viscious Death was proc'ing from "burn damage" being applied by 1 player, if the kill stroke came from another, like many people believe it is. Then I see people in this forum still debating something that was settled long ago.

---

The hardcore PvP guys, the ones that play 50-60+ hours a week, the ones that hold emperor time and time again, don't play in forums much. In fact, I might be the only person in any of the guilds I know who ever comes to forums.
- It is common knowledge VD procs early in PvP on PS4. Join a PvP guild, a serious one. and start telling them you did a "test". You have guys that die 200X a night, they don't do test.----

I was killed by a single Ballista Bolt, in single combat which proc'd VD. there was no lag, I was by myself. there was no other damage from somewhere else.... clear as day. How many of you even knew siege weapons were proc'ing VD? Maybe someone should go run some "tests" on that?

The only person lying is the guy who said he "rolled an alt". Got him to L10, went into Cyrodil and "ran a test" withing 5 hours of me making my last post, LOL... yeah right, sure you did.



You guys keep trusting in the forum, but if your ever in Scourge on a Friday/Saturday playing EP, look me up. I play by the same name. I'll introduce you to 50 guys who play like the game is a full time job (some I don't even know where they get the time) and you can tell these guys who die a few hundred times a week each, that you ran a test on a forum. -- Maybe after running a full group for a few hours, getting enough PvP experience you'll see a long with a couple other bugs "that don't exist" according to ZOS. The only way your going to find this out is by extensive play, not two or three attempts to see something in a controlled environment.

1. You don't even know how much I PvP
2. I know of plenty of bugs that exist, which ZOS fail to acknowledge
3. I'm trusting evidence I did by myself, not some random in the forum who's shouting out with no evidence themselves (which is what you are doing btw)
4. My first bit of analysis was actually done by a Coldharbour Bolt
5. Do some tests yourself to see if it's actually proccing

Rohamad_Ali

If we go by this threads statistics it's 25% 100% allegedly bugged with a 20% margin of error because I have no idea what some posters decided . Can we change the title ?

bowmanz607

Crom_CCCXVI wrote: »

OK Here is the Deal..
- I came to these forums because I was trying to find out whether Viscious Death was proc'ing from "burn damage" being applied by 1 player, if the kill stroke came from another, like many people believe it is. Then I see people in this forum still debating something that was settled long ago.

---

The hardcore PvP guys, the ones that play 50-60+ hours a week, the ones that hold emperor time and time again, don't play in forums much. In fact, I might be the only person in any of the guilds I know who ever comes to forums.
- It is common knowledge VD procs early in PvP on PS4. Join a PvP guild, a serious one. and start telling them you did a "test". You have guys that die 200X a night, they don't do test.----

I was killed by a single Ballista Bolt, in single combat which proc'd VD. there was no lag, I was by myself. there was no other damage from somewhere else.... clear as day. How many of you even knew siege weapons were proc'ing VD? Maybe someone should go run some "tests" on that?

The only person lying is the guy who said he "rolled an alt". Got him to L10, went into Cyrodil and "ran a test" withing 5 hours of me making my last post, LOL... yeah right, sure you did.



You guys keep trusting in the forum, but if your ever in Scourge on a Friday/Saturday playing EP, look me up. I play by the same name. I'll introduce you to 50 guys who play like the game is a full time job (some I don't even know where they get the time) and you can tell these guys who die a few hundred times a week each, that you ran a test on a forum. -- Maybe after running a full group for a few hours, getting enough PvP experience you'll see a long with a couple other bugs "that don't exist" according to ZOS. The only way your going to find this out is by extensive play, not two or three attempts to see something in a controlled environment.

There are many pepole on these forums that play this game endlessly and have been doing so much longer than you console players. You talk as if no one on these forums has a clue. That anyone who plays for an extended period of time or is hardcore does not come here. You are wring. Just because your guild mates that play a lot and are hardcore according to your standards don't come here, does not mean others don't come here. In fact, I find it quite funny that these hardcore PvP players who play in your groups are dieing hundreds of times a week. I usually run any where from 6-10 hour sittings every time I play. I die roughly 18 times a night solo. When in a griup, I die about 9 times a night. I am by no means the best at this game. I am a very solid PvP player though. That said, I already question the quality of players you say are hardcore and would know the set is broken just based on your death count alone.

I also love how you talk about how everyone on the forums lies and can't be trusted, but yet you think we should trust your post for some reason. A post with no proof. A post with a bunch of accusations based solely on your word alone which discredits whatany others no not to be true. If anyone is spreading this false info it is you.

Many of us have tested this set in various environments and what not. The bug is simply a ui error. Every video posted that claims to show VD proc'ing early really shows the opposite when the video is slow downed and calculated properlly. I have seen one video that shows that the set might proc early. However, that. Ideo shows one test against a player that seemingly has a health dysync. I and others have asked this person to show more tests outside of the one to establish that there was no health dysync and have yet to get a response. This leads many of us to conclude the video was a fraud.

Again, many of us on here are hardcore players contrary to your opinion. We have tested it and realize it does not proc early. You can bring 50 people that say it procs early and I can bring the same saying your all wrong. Until there is some proofs outside of the word of a forum post which you yourself said not to trust, the set us working properly and there is nothing to the contrary. I won't rehash the other arguments in this thread about the other possible and valid reasons why your death recap was the way it was and why it seemingly proc. (That is of course assuming your telling the truth.)

On a side note, the set does proc off of siege when a player dies. This will be changed in db.

Nilmot

TLDR: Console player claims his hardcore status as evidence of something. Is shouted down by actual evidence. As further evidence, reiterates that he plays a lot. Players using grown up version of game still not convinced.

Bone_Demon

Isn't this evidence enough?
https://www.youtube.com/watch?v=sRnfs6Hq278

Sunburnt_Penguin

Bone_Demon wrote: »

Isn't this evidence enough?
https://www.youtube.com/watch?v=sRnfs6Hq278

Not for me. I watched this and then recorded 5 or 7 separate occasions where this same animation occurred. In every video I'd already taken enough damage to kill me before my health showed as zero and the VD damage & animation showed up.

Edit:
What would have been enough (and easy to do, I might add) would have been to note the full health and allow us to deduct every single damage given before the VD animation. That way we'd actually be able to determine if the VD damage was proc'ing whilst health was remaining.

GreenSoup2HoT

Vicious Death: Fixed an issue where this item set’s proc was appearing on the Death Recap of the player it triggered from.

PTS 2.4.3

bowmanz607

Bone_Demon wrote: »

Isn't this evidence enough?
https://www.youtube.com/watch?v=sRnfs6Hq278

This is the video where it looks like there is likely a health desync. There is only one test. When asked to repeat the feat there was no response. This is the only video people can point to and is suspect at best. Notice the health that still shows as remaining when the player is dead. This is evidence of a health desync. But alas, people just look at videos and take them for truth without stopping to analyze the and break them down. Yoh know how many videos were posted by people saying the set was broken, but when you slowed it down you could see it was proccing properly? A good amount. This video has received ton a scrutiny for a likely health desync on one test that starts with the player already with lost health. When confronted, no response was given. This video shows nothing but another common bug in the game that likelynoccured.

leepalmer95

Nilmot wrote: »

TLDR: Console player claims his hardcore status as evidence of something. Is shouted down by actual evidence. As further evidence, reiterates that he plays a lot. Players using grown up version of game still not convinced.

You mean easy mode version right? Add - ons = easy mode.