It at least drops combat reliably now. It just doesnt do so instantly like it should. So to feign trap I have to
Feign
wait like a global while combat actually drops
Hit my trap when its usable after combat finally falls.
Stand up and resume.
This is fine as Im a PvE carebear and this is just me doubletrapping in instances for utility… But this would be a disaster of a non-usable system in PvP, so I feel sorry for my competitive brothers.
The problem appears to be that once an attack is queued it executes, even if delayed by CC, an interrupt or is otherwise aborted.
This is not proper and should be fixed.
This dev bunch. . . aren’t really up to it, I’m afraid.
Yeah, this even happens to player-characters. I was put in an ice-block by a mob last night and my pet and dots finished it off. I was leveling my dagger skill on it at the time and when the ice-block ended my character did one more auto-attack to the air, lol.
Did this get changed or their temporary fix reverted? I’m getting the bug again where no FD animation or effect happens at all but it consumes my cooldown. This is while standing completely still, no hands on movement key or mouse.
One thing that hasn’t been addressed by the blues is the pet.
There is a very detailed testing video on youtube called Classic Hunter Macros - Traps (Feign Death, Bugs and Workarounds), by muhshuh. I’d appreciate if someone would link it as I’m new to the forums and thus blocked.
Another thing that comes to mind is how queuing and batching could be affecting this combo. What I think is happening is Feign Death + drop combat is happening in one batch, making the trap unusable and thus delayed until the next batch is processed. That would result in a minimum of 401ms for the combo to execute + one’s input lag, assuming the command reaches the server right as one batch is about to end; the maximum, then, is 799ms. Worse yet would be if Feign Death cast is happening in one batch, dropping combat on another and casting the trap on a third one. Both seem plausible given what I’ve observed. With 200ms, I have to be lying on the floor fully dead before the trap appears, spamming the macro. Way too long.
Regardless, Feign Death + exit combat + lay trap should have absolute priority in the batch if batching is to work as intended: so two people can cc each other at the same time (is that really worth the server lag???).
I’ll say it again: Feign Death + exit combat + lay trap should have absolute priority in the batch. Anything else results in a fail.
Also, take a look at that pet interaction.
why have almost every private server been way better than the original?
i trapped a lvl 49 (as a 60) and the trap lasted less than 5 seconds. why is ice trap so short?
who the **** hates hunters at blizz office to complete nerf them?
I don’t really have anything to add at this point. Everything has been reported and well documented so at this point it is up to Blizz.
It has been 1 month since the first blue post, so I would imagine there will be another development soon, hopefully.
Just bumping to make sure no one (Blizz) can pretend to ‘forget’ about FD being comically bad.
Pserver was better because it used the original reference client.
Yes, the port is garbage. Between these bugs and leeway, combat is SO materially changed.
It seems that any melee or spell attack, even if interrupted, is allowed to complete, once your “interruption” is done. Which obviously is NOT the way combat works. An aborted attack should be just stopped.
Yep. Aborted attacks still continue. Sap + bandage does not work because, even though they are sapped, their auto attack goes through (while under the affect of sap), dealing damage and breaking the bandage.
Same thing as cheap shot (rogue stun opener). You can cheap shot an enemy from stealth to stun them, but they actually auto attack you after you stun them. Unreal! And blizzard STILL hasn’t even acknowledged this.
An obvious and fundamental BUG
Lol are we gonna make it to 1000 posts with this still being broken?
God damn I feel sorry for you hunters. Just know we druids have it just as bad.
I’ll allow you to viper sting the next druid you see in bear form to show my support
Rogues have it bad too. Seems like the only classes that are not ultra buggy are mages, paladins, and to a certain extent warriors. Go figure…Blizzard loves mages.
Bump bump bump.
To my knowledge and experience viper doesn’t remove mana in bear like mana burn does.
any updates? I would think this should be a top priority as the BG update will be coming around pretty soon!..
Mana burn isn’t supposed to affect a shapeshifted druid…
Agreed, just saying viper sting is not draining mana
Let me break down exactly how spell batching or whatever they call this is complete garbage
Watch this pull
Look how long the mobs lag before they turn to attack. The serpent literally ran through the agro range AND the mob, attacks the caster, THEN STARTS RETURNING before the group turns to attack
Again, look how long it takes for the dogs to drop agro after he feigns
To any trained eye this looks flat out JANKY, like the worst private server lag you could imagine.
Mages are absolutely broken as well. I rerolled a mage and when AOE farming, the delay it takes for a mob to recognize you are in it’s aggro range completely kills AOE farming. For example, you’ve aggroed 2 NPC’s, now you’re running toward the 3rd and 4th NPC’s. It takes them about a second to recognize you are within aggro range so you either have to stand there like an idiot and wait or continue running toward them until you’re literally standing on top of them. Either way, you will be getting hit many times. You will be at 50% health or lower by the time you cast your first Blizzard. Inc 1 shot by rogue.