Sub Assault often hits twice in one cast

zyk · March 2019

anatole1234 wrote: »

Can confirm getting double hits of sub assault

@anatole1234 How have you confirmed it?

It's not that I doubt anyone, but I'm surprised no one with a proper combat log has captured it yet.

Ralamil · March 2019

Solariken wrote: »

The native death recap is indeed a crappy tool but I swear to all things holy this was an instagib.

But surely you can understand why folks are asking to see something more concrete for confirmation than just your word and a screencap of a tool you yourself admit is crappy. I don't even necessarily think anyone believes that you're outright lying intentionally, just worried that you might be missing something which is causing you to view the ability as hitting twice in a single cast.

Solariken wrote: »

I've seen it a huge number of times and have many friends that have confirmed this happening. This was Shor PC/NA ~120 ping. I've seen it many times in BGs as well where there is rarely any lag. Also, 3 seconds is an ETERNITY in PvP combat. I can break free, heal up, and counter CC before a second subA hits me.

For instance, do you think it's possible that the death recap is simply showing you the hardest hitting abilities that damaged you prior to your death in the same instance of being "in combat," and that at some point a little earlier in the fight the warden maybe clipped you - hard - with shalk, but you survived/healed through it? And then later he combo'd you, instantly killed you, and that combo plus that earlier shalk were the hardest hitting abilities, thus showing on your recap?

IF this ability is hitting twice per cast in some instances, then yes it absolutely needs to be fixed. But I'll remain skeptical until someone can provide a parse or video that provides clear evidence of it occurring, rather than a simple death recap. The recap simply obscures too much to be reliable.

EDITED: Clarified a section of text, fixed punctuation.

Solariken · March 2019

Ralamil wrote: »

Solariken wrote: »

The native death recap is indeed a crappy tool but I swear to all things holy this was an instagib.

But surely you can understand why folks are asking to see something more concrete for confirmation than just your word and a screencap of a tool you yourself admit is crappy. I don't even necessarily think anyone believes that you're outright lying intentionally, just worried that you might be missing something which is causing you to view the ability as hitting twice in a single cast.

Solariken wrote: »

I've seen it a huge number of times and have many friends that have confirmed this happening. This was Shor PC/NA ~120 ping. I've seen it many times in BGs as well where there is rarely any lag. Also, 3 seconds is an ETERNITY in PvP combat. I can break free, heal up, and counter CC before a second subA hits me.

For instance, do you think it's possible that the death recap is simply showing you the hardest hitting abilities that damaged you prior to your death in the same instance of being "in combat," and that at some point a little earlier in the fight the warden maybe clipped you - hard - with shalk, but you survived/healed through it? And then later he combo'd you, instantly killed you, and that combo plus that earlier shalk were the hardest hitting abilities, thus showing on your recap?

IF this ability is hitting twice per cast in some instances, then yes it absolutely needs to be fixed. But I'll remain skeptical until someone can provide a parse or video that provides clear evidence of it occurring, rather than a simple death recap. The recap simply obscures too much to be reliable.

EDITED: Clarified a section of text, fixed punctuation.

Yeah I've got CLS running, just waiting for it to happen again.

I'm 100% sure in the recap pictured I was not even engaged yet with the guy who clapped me. He came out of the bushes and plowed me immediately.

I know I didn't give much to go on, but if you read in the thread there are multiple people corroborating. If you PvP enough I guarantee you will see it happen.

Ralamil · March 2019

Solariken wrote: »

Yeah I've got CLS running, just waiting for it to happen again.

I'm 100% sure in the recap pictured I was not even engaged yet with the guy who clapped me. He came out of the bushes and plowed me immediately.

I know I didn't give much to go on, but if you read in the thread there are multiple people corroborating. If you PvP enough I guarantee you will see it happen.

I PvP all the time (stamden is my main), and I have seen shalk from the same person multiple times on my recap plenty of times. And not once did I think it was a case of a single cast hitting me twice. When I get burst down instantly, it's usually 2+ people (or one really skilled ganker but those are usually NBs). And when MY shalk go off, I don't ever recall seeing it pop up in my UI as having damaged someone twice.

I read the thread, and literally no one provided any more corroborating evidence than you did (in fact, most of them gave LESS, since at least you provided a screenshot. As lacking as I think that was overall, it was at least something). Most simply replied "yup, seen it," or in the worst cases tried hijacking your request for a bug fix to get on their "nerf warden" soap box.

Like I said, I'm totally onboard with this getting fixed if it is indeed a problem. I just want to make sure that there's legitimate, irrefutable proof that something wonky is going on, with something more substantial than a single death recap to go off of.

So, good on you for running CLS to try and find that "something more substantial!"

Recremen · March 2019

Where is the DoT damage for the Dawnbreaker hit? Is it possible the second sub assault hit is being incorrectly attributed, and that damage is actually coming from the Dawnbreaker DoT?

Solariken · March 2019

Recremen wrote: »

Where is the DoT damage for the Dawnbreaker hit? Is it possible the second sub assault hit is being incorrectly attributed, and that damage is actually coming from the Dawnbreaker DoT?

I didn't live long enough for the DOT to tick haha. The combo was perfectly timed on his part (not difficult to do honestly). He even kb'd me with the bash cancel as a cherry on top.