Question on Feign Death

I haven’t leveled my Hunter yet to test it, but i did play Hunter a lot in Vanilla.

I didn’t have issues with Scatter Trapping people so FD wasn’t an issue back then.

So my question is: Is the issue with FD the lag between casting it and dropping aggro?
If so, is Classic’s “Spell Batching” to blame?

Yes spell batching is to blame. Blizzard identified the issue but haven’t fixed it yet.

Take a look at the blue posts.

It seems the only bug left with FD is the turning bug

Not really:

Hunters are naturally very concerned about the behaviour of this iconic skill, with a variety of important uses, and I want to assure you that we are aware of your bug reports and that we are actively investigating.

These bugs are not easy to detect because, in our reference builds, we find the same reports but only with a slight difference in timing or consistency, which makes their identification difficult. Despite this, we have made some progress.

The first issue is that Feign Death cancels when you move, including if you turn, and very often high-skill hunters are running from an opponent, turning to shoot behind them, and then Feign Death to drop a trap. It some of these cases, Feign Death is failing because the spell-cancel on turning is more sensitive in WoW Classic than it was in 1.12.

We’ve tracked down why it’s more sensitive, and we’re testing a change now that relaxes the spell cancellation to make it less likely that you’ll inadvertently trigger this if you’re trying to stop turning to cast Feign Death. That said, if you continue turning after the cast, or keep turning during the cast, you can still cause Feign Death to be cancelled.

There are other reports about it taking too long to drop combat, or having combat re-activated because your pet is getting attacked, and we’re still looking at those issues. We’re tracking a couple of leads there, but we haven’t got this bug in our sights yet, so it may take a bit more time to figure out what’s really going on here.

I’m sorry it’s not a silver bullet, but hopefully it gives you some peace of mind to know we’re listening, and still investigating the issues. - Pazorax, Wow Dev

They changed the batching queue but that hasn’t solved the delay of abilities caused by batching.

This is because the so-called “batching queue” does not recognized an aborted attack.

Mob attacks
You deflect/interrupt with CC, interrupt, aggro drop – YOUR interrupt should cancel/abort the attack.

Instead:

mob attack merely delayed until your interrupt effect is “over” either because it completed or failed.

Bottom line: CC, interrupts, aggro drops should abort the incoming attack, not merely delay it.

1 Like

I’m convinced Blizzard can’t get anything right these days and should abandon batching/leeway until they figure out how to implement it without totally screwing up game play.

1 Like