There is bug/mechanic that if you activate bladestorm a split second after some CC (e.g. polymorph) you get only cc’d for half of the duration.
Blizo was taking advantage of this bug/mechanic during AWC Summer cup #5 and could get some nice kills ! sometimes it happens during ‘vision of perfection’ proc but still i just wanted some confirmation that is this intended or is it just a bug?
you can see exactly what I mean in this video @ 21:00
i’ve had this happen on my warrior as far back as early legion but usually only with stuns like if i bladestorm right when kidney or sweep happens i get the stun i go on dr then bladestorm starts
this was in the game forever, if u bladestorm same time u get ccd it breaks u out of cc
5 Likes
Seems like an ms thing that should stop one of the abilities from going through. I’d say a bug, or clever use of game mechanics.
yeah i heard both side of stories. some say this is an old bug and some say this is just a clever use of mechanic which is actually kinda hard to pull.
Have you ever kicked a cyclone and still got cycloned? It’s not a bug, it’s called the reality of playing a game on the internet where people are hundreds or thousands of miles away and pushing buttons at the same time.
This has existed since Cata
If you have fast enough reaction time you can do it
It basically lets you use bladestorm as a trinket if you use it the exact moment you get CC’d
4 Likes
i’ve only ever seen it work proactively, same as deliberately bladestorming a cc but you get further rewarded for cutting it closer by being on DR for whatever you immuned
if it’s actually usable reactively that seems wonky, but very technically kicks are reactive and latency still dictates those are more landed and juked by prediction than reaction so 
youve been able to bladestorm cc forever, its something something about latency and communicating with the server in batches or something like that
its pretty much in the same neighborhood as deathing cc (the actual sw:death not this casual ez mode premonition garbage)
things going off at the same time, kinda like how 2 rogues can sap each other out of stealth, or shadowstepping charge, blah blah
if you press bladestorm at the same time you get hit by cc it will go off, and since u cant be ccd in bladestorm it breaks u out. as the years have gone by blizzard’s servers have gotten much better with communicating with ability use so its far less common, but they are replicating the effect on wow classic so you will kinda understand better when thats out
When I use to play my warrior I use to spam bladestorm when sapped and it would sometimes go off when the rogue opened
It might be a bug but has been in the game for a while
And honestly I think it should stay. It is a very highly skilled played that takes great timing to pull off
To bad there are not more abilities like this
my question is : is this intended ? is this intended to use bladestorm as a trinket ?
and if this is not intended, why this hasn’t been fixed?
It’s similar to the shadowmeld mechanic where if you time it right you can avoid the cc. You have to anticipate the cc the exact second it goes off in order for it to work.
I personally like the mechanic, as well as mechanics that are similar. However, I’m biased for I play war.
Visions used to break you out of CC, however I believe they fixed that.
I never viewed it as a glitch more a chance to outplay your opponent. I use it all the time if i know a stun is coming ill preempt with a BS. Some times if i time it perfectly the stun will land as i BS and my BS will override it.
I enjoy this because its one of the few area’s in my class i feel like i can still exibit some form of skill or outplaying with all the pruning we have had.
Honestly, this is way easier to do than they made it sound in the tourny and pretty common.
The real problem is ghost wolf doesn’t break cc and put it on DR.
Buff Enhance.
bladestorm needs to be worse for damage before we go around putting medals on people who bladestorm cc
like meta-ing cc, it’s easy to do by complete accident when it’s one of your strong offensive cds and the enemy team is already encouraged to be using peels at the time you would want to pop it to capitalize on pressure
edit: yes, turbo fists parry is in exactly this boat, except that if the game decides to let a tick of it go through at the same time as a kidney shot the monk will still be stunned for 6s
It’s reactive but you basically have to react the moment you get hit by it
It’s a lot easier to do it on casted CC because of that, but getting it on kidneys is more important
I think thats why vs rmd Blizo will opt out of safeguard for visions of perfection just because he sees more value in storming out a go than conflict vers
1 Like
After reading all these comment, i believe that Bladestorm shouldn’t be acting like a trinket and this is just an old and ignored bug.
i mean, kicks are reactive, but latency prevents it from actually being possible to do something reactively in that way, that fast, consistently, without being an 11 year old on hardcore drugs
that’s why people kick bandages; it’s possible to prep yourself for something you know is coming and then react relatively fast, but it’s not possible to actually make decisions in cognizance of the data you’re being given that newly affects that decision-making
this becomes a kind of chicken vs egg thing if you really strip it down, i think: is the warrior prodigy reacting purely to the fact that he was kidneyed, at robot speeds, or is he reacting to the slight movement a rogue made towards him an instant before using shadowstep
my take on it is that calling things like this reactive is technically accurate but leaves out some of the middle, but i’m also 25, and i’ve never been even passable at a videogame that didn’t have global cooldowns, so i could just be way off