@Solariken Not only are you defending a bug, but you are telling people to L2P against a bug that specifically rprevents counterplay. And calling me cranky now?
Also Please stop with your strawmans about other CC skills and fast killing builds. None of them are relevant to this bug.
Anyone still defending this skill should be aware that you're tossing away a lot of your personal credibility. It's the same thing we see every patch. People saying Viper was fine. Sload's was fine. Torug's Enchants were fine. Yadda yadda.
In all those past cases, there was blindingly clear evidence about the content in question being WAY out of whack—but we still had a select handful of individuals who seemed to think prancing onto the forums and swearing that everything was all good and dandy would magically make devs and players alike forget their woes and move on, leaving them to continue abusing the crutches they've grown to love and rely on.
Do you guys ever learn?
Right now we have multiple clear, documented bugs with this skill:
- Cannot break the knockback
- Attempting to break during the knockback puts you on cooldown, meaning the hard CC becomes unbreakable
- Knockback doesn't apply CC if the caster LOS' or gets CC'd—leaving the target open to multiple CCs subsequently
These are known facts, and no amount of misdirection and smokescreens on your part is going to dissuade others of them.
You're just ensuring no one takes you seriously in future discussion.
Anyone still defending this skill should be aware that you're tossing away a lot of your personal credibility. It's the same thing we see every patch. People saying Viper was fine. Sload's was fine. Torug's Enchants were fine. Yadda yadda.
In all those past cases, there was blindingly clear evidence about the content in question being WAY out of whack—but we still had a select handful of individuals who seemed to think prancing onto the forums and swearing that everything was all good and dandy would magically make devs and players alike forget their woes and move on, leaving them to continue abusing the crutches they've grown to love and rely on.
Do you guys ever learn?
Right now we have multiple clear, documented bugs with this skill:
- Cannot break the knockback
- Attempting to break during the knockback puts you on cooldown, meaning the hard CC becomes unbreakable
- Knockback doesn't apply CC if the caster LOS' or gets CC'd—leaving the target open to multiple CCs subsequently
These are known facts, and no amount of misdirection and smokescreens on your part is going to dissuade others of them.
You're just ensuring no one takes you seriously in future discussion.
@TheYKcid I say this with love, but let's not forget which side of the Rune Cage fence you were on when that was the most OP CC in the game by a country mile.
GeneralSezme wrote: »Anyone still defending this skill should be aware that you're tossing away a lot of your personal credibility. It's the same thing we see every patch. People saying Viper was fine. Sload's was fine. Torug's Enchants were fine. Yadda yadda.
In all those past cases, there was blindingly clear evidence about the content in question being WAY out of whack—but we still had a select handful of individuals who seemed to think prancing onto the forums and swearing that everything was all good and dandy would magically make devs and players alike forget their woes and move on, leaving them to continue abusing the crutches they've grown to love and rely on.
Do you guys ever learn?
Right now we have multiple clear, documented bugs with this skill:
- Cannot break the knockback
- Attempting to break during the knockback puts you on cooldown, meaning the hard CC becomes unbreakable
- Knockback doesn't apply CC if the caster LOS' or gets CC'd—leaving the target open to multiple CCs subsequently
These are known facts, and no amount of misdirection and smokescreens on your part is going to dissuade others of them.
You're just ensuring no one takes you seriously in future discussion.
@TheYKcid I say this with love, but let's not forget which side of the Rune Cage fence you were on when that was the most OP CC in the game by a country mile.
Rune cage is not as widely used anymore and now has counterplay to it, there is literally no punishment to a bowtard that spams draining shot or petrify, or time stop or flame reach or any cc that doesn't require any resource to use or that you be in the face of the people you are trying to zerg.
Oh I used the *** out of it during Summerset. It was nice to have Sorcs on top for a patch.
I never claimed it was fine, though, and openly admitted it was overtuned to anyone who asked.
It got nerfed (overly so, I still maintain) and we moved along. I do fine without it, as should the players using Draining Shot once it gets fixed unless, of course, they WERE actually crutching on the skill's brokeness, and can't cope without it.
@Solariken Not only are you defending a bug, but you are telling people to L2P against a bug that specifically rprevents counterplay. And calling me cranky now?
Also Please stop with your strawmans about other CC skills and fast killing builds. None of them are relevant to this bug.
@del9 and others here's the thing:
There is zero evidence that the normal function of this skill is bugged in any way. The CC portion of the skill has been exactly the same since day 1. The only thing they changed is projectile range.
In fact I would argue that the skill functions 100% as intended. Look at it like this:
The vast majority of ranged skills are dodgeable, reflectable, and blockable. Landing a hard CC is the only window a ranged build has to secure a follow-up. It also happens that the main spammable for bow has a 1.1 second cast time. Without a proper CC like DShot, landing a follow-up and securing a kill would be impossible. The knockback is also important because increasing distance is the only way bow skills deal respectable damage.
So please tell me more about how this skill prevents counterplay? A dodgeable/blockable/reflectable projectile with a conditional heal that does terrible damage. How can you say that with a straight face?
dwemer_paleologist wrote: »the same exact thing happens in that video as all the other CC's and stuns.
and you proved also in the video that it happens very rarely just like all the other CC's do.
its not broken, its lagg.
and how lagg effects cc's
all of them.
Can be dodged, blocked, reflected, gets called unavoidable..... lol
It doesnt have disorient either...
Has singular purpose of CCing target with petty damage not even close to anything like frag lol...
OP are you bad? or just mad?
the knockback part of it is not CC-breakable. And when lag hits it just gets exponentially worse.
Single purpose = only does 1 thing
draining shot does:
- Buggy ass CC
- Meh damage
- Draining shot specifically heals for an decent amount
- with BRP bow puts a dot on you
- guarantees the next snipe you queue to land
"no disorient"
Blast an enemy with an explosive arrow, dealing x Physical Damage, knocking them back 6 meters, and disorienting them for 1.5 seconds. After the disorient ends, you heal for y Health.
source: https://eso-skillbook.com/skill/draining-shot
Oh and its available on every class.
I mean in your signature you linked a Bow/Bow guide for PvE, so I cant take you serious anyways. just gtfo.
Yeah listing info from some outdated website instead of knowing what it does in game sure helps your argument lol. Seems I cant take you serious and nor should anyone else
dwemer_paleologist wrote: »the same exact thing happens in that video as all the other CC's and stuns.
and you proved also in the video that it happens very rarely just like all the other CC's do.
its not broken, its lagg.
and how lagg effects cc's
all of them.
Then you should have no problems with the skill's CC mechanics—and the CC mechanics only—being recoded to function like Dizzying Swing.
You still get your knockback > stun.
You still get your heal.
You still get your damage.
The only thing that would change, ostensibly, is a buggy CC behaviour that according to you and others doesn't exist, anyway. So you—and other "legitimate" Draining Shot users—would have zero logical reason to oppose ZOS investigating the issue.
dwemer_paleologist wrote: »the skill is fine, that break free slow part is from lagg. nothing new.
and by the way "it is not spammable, once you are hit with it we cant repeat untill that swirling thing is no longer on you, and that takes a while. its not spammable.
us archers and ranged playstyle players need a way to keep you at a distance so we have a chance to survive instead of killing us so fast.
allows us a chance at survival. and gives us a chance to perform long range distance like we are built for.
the complaint your talking about, is from lagg, all the CC's and crowd controls in eso have allways been prone to lagg problems and this draining shot is just the same as the rest of them.
Mrsinister2 wrote: »I get hit with it constantly with no follow attack or anything I'm pretty sure people do it just to be annoying.
Is it because the stun is 1.5s and starts from when your hit not when you have been knocked back. So by the time you have been knocked back you cant breakfree because you are no longer stunned?
Gone are the days of interactive combat.
Zergs spam timestop and scattershot on you and will only confront and chase you when numbers are clearly in their favor. Their Confidence increases as more players of their faction add on to the already disproportionate fight.
Ill add a clip later to show what I mean.