i have now had serveral back to back shuffle matchs where i could not cast btwe with full combo points wether from stealth or just plain as outta stealth i can spam it all i want but nothing happens like what in the hell is going on with this game even shadowlands wasnt this buggy
<insert “first time?” meme>
3 Likes
honestly yes i never had this issue is bfa/shadowlands/dragonflight but since the release of war within ive had the bug happen an insane amount completely ruining burst windows now that are burst is so reliant on crackshot
I remember it at the start of season 3 briefly before it got fixed fairly quickly.
Some people apparently remember it from BFA. It’s not new but it’s definitely far worse.
Literally the first thing I was about to post as soon as seeing the thread 
I can personally confirm as far back as Shadowlands that it was an issue. Considering that we weren’t tied to vanish weaving our rotation then, it wasn’t as persistent or frequent. Crackshot’s spamming combined with vanish weaving and subterfuge now opens a huge number of windows more for it to break. And a lot more points for it to break at.
I still haven’t seen a solid reason as to what causes the break. There’s an order of operations you can make involving cheap shot that guarantees to break it, but this also happens in raid and keys, where I basically never use cheap shot for any reason beyond a panic interrupt.
I -think- I’m noticing it a lot when I vanish into a BtE too quickly. Which is stupid since it feels like you’re being punished for playing a high apm class exactly as intended.
It literally happened just 10 minutes ago on a dummy but between trying break my habit of AR before the duration is over, making a mental note of roughly how many times I’m using RTB in a 45 second window, I’ve already forgot what I even might of done to cause it.
Edit: Literally just did it again. BtE on cooldown when used inside a crackshot window. What the actual f.
Edit: …and again.
I know that’s definitely one of the failure points. And one I saw looking at some logs myself just now.
The problem feels like a latency issue on that one, at least sometimes, as I basically never had this problem after it was adjusted in DF S3, but now suddenly have it constantly. The logs were showing an actual .01 second window between the casts, which I can see the system not tracking in order occasionally. I also know I’m a human who is prone to mistakes, and a large chunk could be my fault. Though, to have the timing for months without having issues and suddenly “messing” it up constantly seems a bit unusual, even if a percentage are absolutely my own fault.
But, I know some of the breaks aren’t related to the overlap. I’ve waited almost a full second between inputs on days that I’m just exhausted, and have still had it reject the BTE activation.
I just think there are too many points of failure with the design. It’s probably 5 different problems that compile into the same response from the spell.
1 Like