[Hunter][PvE][PvP] Explosive Shot

[Noshlo]

Wowhead/WoW Freakz Link: https://www.wow-freakz.com/spells.php?spell=53301&&name=explosive-shot

Descrierea bugului / Bug description: Explosive Shot's DoT is clipping, and it shouldn't.

Dovada / Proof: It's very easy to check in-game, a screen shot won't prove much. A video will work best but I don't really want to do it. I'll do it if I'm required to.

This bug has been posted once and rejected as a duplicate, then again by me since I didn't see the duplicate bug report since I didn't think I needed to search in "fixed and rejected bugs", but a GM clarified that a confirmed bug report about DoT and HoT clipping will fix this issue when it is fixed. It has not. I've checked this many times since, either by waiting a tiny bit after the Explosive Shot gcd has finished or by waiting for the Eplosive Shot to almost fade off the target and then quickly applying a new one, and it is still bugged.

previous bug reports:
http://forum.wow-freakz.com/DUPLICATE-Hunter-PVE-PVP-Explosive-Shot-Lock-and-Load-t222068.html
http://forum.wow-freakz.com/DUPLICATE-Hunter-PvE-PvP-Explosive-Shot-t259538.html

Thank you, and please don't reject this again rage, if you need proof this is bugged ask me for a video.

[Rageless]

Oh well .. I've tested this 60 minutes with Groovy again and again, he can confirm ... but CHECK NOW. Works fine for us and seems you're the only who is QQing here about this. Bring me that video as proof, I will make one after.

[Noshlo]

http://imgur.com/CSyrV93

I'll try to make a video as soon as I can

In order to reproduce you ofc need the second Eplosive Shot to land before the first one finishes ticking.

Edit: http://tinypic.com/player.php?v=281ev13&&s=5#.UndeTvkQ7h4 there we go. sorry for the low quality.

[ZickZak]

Rage. wrote:

Oh well .. I've tested this 60 minutes with Groovy again and again.

You were testing this for an hour? How?

The question is not if, but how should it work? I didn't do any research, but from what I remember, two explosives weren't able to clip either way - the last tick can stack with the first one of the next shot, but not two. Hence shooting two ES in a row could not clip. The reason for this is due to a patch and its dot change mechanism - before, casting dot with 1 tick left overwrote its effect. In this patch, casting a dot with 1 tick left adds the dot to the previous, which makes it start after the previous finishes = why you delay 3rd ES, the second one's "longer". The first two could clip only in case you have extremely low latency, as the 2nd one would start right before the second tick of the 1st ES, which, luckily won't be problem for anyone as even 5 ms is enough.

Again, I'm not sure if that's true. You guys will have to google or I'll try to later on.

https://youtube.com/watch?v=PJ7nxQMc-Yc:

.be

[Rageless]

@ Groovy

[Tzopaluca]

http://forum.wow-freakz.com/DUPLICATE-Hunter-PVE-PVP-Explosive-Shot-Lock-and-Load-t222068.html
Nu a fost ok dupa ce s-a reparat "aia".

[Noshlo]

Tzopaluca wrote:

http://forum.wow-freakz.com/DUPLICATE-Hunter-PVE-PVP-Explosive-Shot-Lock-and-Load-t222068.html Nu a fost ok dupa ce s-a reparat "aia".

Why should I reply if you don't read my post? Unless I didn't understand what you said, I used google translate.

[nero]

Using these sources as a reference :
-> This , "With damage over time abilities now refreshing without wasting a dot, "interleaving" a cobra shot between procs is less viable. Instead we can more quickly use our explosive shots without wasting charges. Simply spamming Explosive Shot will result in 8 ticks, with 1 lost. Before 4.2 this would have been 7 ticks. If you wait a small fraction of a second after the 1 second GCD, it should be sufficient to get all 9 ticks quickly. This would be 9 explosive shot ticks in about 3.3 seconds assuming you wait 0.1 between each. This is almost always the best usage on single target, although there may be times when filling in an instant cast ability such as kill shot is worthwhile."

-> This , "Unfortunately, “most conditions” are not “all conditions.” There are some situations (as commenters below point out) where having no delay between the first and second ESs results in clipping. One such situation is when you are moving toward the target. This causes the ESs to arrive too close together and clip. Because of this it helps to make sure that you are not firing the second ES in a LnL sequence before there is one second left on the first ES. Zeherah cautiously recommends using an addon to watch fractional seconds. I personally recommend NeedtoKnow for this but other addons may work too. Regardless, to be on the safe side, I recommend putting a slight delay (but, again, not a shot) between the first two ESs in a Lock and Load sequence. This delay should be very small, substantially shorter than a global, and I recommend testing it out yourself on training dummies to get a feel for what works for you."

=> Now again on how it should work :
- It's impossible to clip ES before it ticks twice due to gcd .
- It may clip only if it is refreshed after the first 2 ticks of the previous ES have occured , a little over the 1s gcd with 0.1s-0.2s ish being the limit as the guy from the EJ thread mentioned ( and so did the others calling it a "slight delay" ) not taking into account the connection problems or pc issues regarding client server communication ( that's just crazy perfect conditions ) BUT it happens nevertheless .

Right now on Freakz the last tick/'s disappear all altogether because the dot is not clipped but rather replaced entirely .
To portray this in a more understandable situation ( sitting near the target dummy so there is no travel time ) :
-> 1 < If you shoot only 2xES's in a row with a LnL proc and no delay before the first gcd (/ES cast) it might seem to work rather okay, the clipping part that is , giving you just 5 ticks . But if you delay the second ES just a little bit more than 0.5 you will see the false "clipping" occurring but that is just the new ES dot overwritting the old one .
-> 2 < LnL proc > ES > ES > LnL proc fades(is used) and apparently there is no 1s gcd here loosing 2 ticks here too > ES , with no delay between ES's will result in 6 ticks instead of 8 .

" you are "