I agree with you 100%, what we all paying for??? A subpar experience and I’m fed up, where is the money going to? If they can’t fix broken classes in a timely matter making this much money then I don’t know…Seems too many things are just broken.
and the folks sticking up for blizz saying oh you just have to macro…uhm, no you shouldn’t have to use a macro for any of your instant abilities period.
After doing some research on another thread, maybe every single hunter complaining of fd/trap not working as it did in Vanilla, needs to go and read the patch 1.12 data in detail.
Players can no longer drop from combat by repeatedly placing their pet into passive mode.
Here is my take on this whole mess. Its not actually the spell batching directly, its the way it was implemented. That’s to say they some how forgot about ordering. I had a theory prior to the blue post saying FD was fixed that they had messed up the order of things with batching in general.
I figured this was the case of a lot of bugs because of the way spell interrupts are working right now. I dont remember having such issues with kicking/pummel/charge/shield slam etc stopping spells. Right now you better get that spell in the first 1/2 second or everything goes off and your spell interrupt goes on cool-down but they still cast. Lets look at an example of charge and trap.
Hunter traps
Warrior charges over trap
Trap goes off
Warrior hamstrings
Now assume that all of these things happen in the same batch. Some of these things make other things impossible ie. if a warrior is trapped he cannot hamstring. So #4 cannot happen. But if they have the order of this messed up on the server it can cause all kinds of weird interactions ie. hamstring while hes trapped. The order is executing like this:
Hunter traps
Warrior charges over trap
Warrior hamstrings
Trap goes off
This can happen with lots of other skills to. With kick for instance. If you have a spell cast in the last 400ms of the cast and you kick it the server will see a batch with kick and the spell casting. What order does it execute the commands? It should say “Well the rogue kicked the spell and thus kick interrupted the cast” but what seems to be happening is that its random, sometimes it works and sometimes it does not. This to me indicates they messed up the order within the batching system. The fix for this (without removing such long spell batching) is to rework the priority system and fix the order of basically everything. Druids have a ton of bugs with power shifting. I bet its due to ordering too. ie.
Shift to cat
apply aura
apply extra energy
but whats happening is more like:
apply aura <- fails because they are not in cat and thus you end up in cat without
Shift to cat
apply extra energy
TLDR: imo the order of skills being executed is wrong on the server side
Because it appears everyone is saying FD/Trap should be instant. The only way it was ever instant was using the PetPassiveMode() script. Show me a clip from after this patch in 2006 where a trap is placed in the same keypress.
Here is a clip of how its supposed to work.
https://www.youtube.com/watch?v=U-BQ_JIcJV4
Notice how he manually stops pet from attacking, clicks FD, and clicks trap, in 3 keypresses. Never was it an instant cast.
Here is a clip of an instant trap exploiting petpassive, and that is the only reason fd/trap was ever instant cast pre bug fix.
https://www.youtube.com/watch?v=WEQd7Ycydy4
This thread should be titled - BUG - Feign Death not dropping combat quick enough. Because thats the only issue with FD atm, not dropping combat in the way vanish is combat bugged.
Have you played a hunter at all in Classic? PetPassiveMode() isn’t relevant because the bug happens even with no pet out.
This thread should be titled - BUG - Feign Death not dropping combat quick enough.
This is pretty much what the entire thread has been about as it stands? It’s FD taking several seconds to drop combat thus making it near impossible to trap, change trinkets, drink, etc.
Why are people still asking for FD/Trap to be instant in the same keypress. I just brought some extra info as to why it shouldnt be.
And the combat/not combat bug is bigger than just FD. Having someone ride past you with mobs chasing them, while you are attacking something, will train all of those mobs on you.
It was never instant without the bug. Understand what im saying. The macro was supposed to be spammed as in not in the same motion.
Step 1 - fd and drop combat. - this is where the bug lies, in dropping combat
Step 2 - cast a trap. will only cast a trap out of combat thus working as intended.
What some of you are misunderstanding and want.
Step 1 - fd and drop combat while also casting the trap in the same keypress.
In the old days did a FD/Trap macro do everything in one button press or did you mash it twice quickly? I can currently FD then trap somewhat reliably, but I have almost trained myself to wait through the delay before hitting my macro again to drop the trap. I haven’t done this in PvP though, this is only against mobs. And they run away as soon as I FD so they aren’t he best test.