Jump to content
FORUMS
Sign in to follow this  
Starym

Feign Death Bug and Upcoming Hotfix

Recommended Posts

f3gCYi3.jpg
 

Here come some more Classic hotfixes, as Blizzard have found at least part of the issue that was causing problems with hunters' Feign Death. It seems the spell cancelling for turning is more sensitive in Classic than it was in 1.12, so it's much easier for the Feign to cancel out. The hotfix will address this issue, but excessive turning both during and after the cast will still cause it to fail, but it will be less likely after the hotfix.

There are other issues also being investigated regarding combat engagement during Feign Death:

Blizzard LogoFeign Death (source)

Hey everybody, I wanted to take a minute to talk about Feign Death. Hunters are understandably very concerned about the behavior of such an iconic ability, with a variety of important uses, and I want to assure you that we’re aware of your reports and we’re investigating. This one isn’t easy at all. In our reference builds, many of the same behaviors that players are reporting do occur, but sometimes with slight differences in timing or consistency, which makes it really difficult to even identify a clear bug in the first place. However, despite this difficulty we have made some progress here.

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. This fix will go out soon as a hotfix.

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.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Staff
      Here come some big spell batching changes to the Classic PTR, with a huge rediction in the batch window:
      PTR 1.13.7 (source)
      Today, we’ve opened the WoW Classic Public Test Realm (PTR) to test version 1.13.7 of WoW Classic. In this upcoming version, we intend to reduce the spell batching delay.
      There are numerous class abilities and spells from Original World of Warcraft that were re-implemented in WoW Classic with spell batching in mind, and we initially expect bugs or adverse consequences with spell batching reduced. In this PTR, testers have an opportunity to join us in finding such issues. Raids and battlegrounds are available in this PTR to facilitate testing in a wide variety of game content.
      Initially, the spell batch window is set to 10 milliseconds on the 1.13.7 PTR, a reduction from the 1.13.6 live window of 400 milliseconds. Please use the in-game bug reporter (default hotkey: mouseover+F6) in the PTR to submit your bug reports or feedback on abilities with spell batching reduced.
      8
      When logged into the PTR, you can mouse over any item, spell, or talent and press the assigned hotkey to initiate a bug report for that item or spell. Bug reports created in this way include valuable metadata about the spell, your talents, and your player-state when the bug is submitted.
      If you’ve unbound your “Open Bug Report” hotkey, you can rebind it in Keybindings -> PTR.
      5
      If you wish to discuss class issues related to this update with other players, we’ve opened a new discussion thread in the WoW Classic Bug Report forum here 34.
      Thank you for testing WoW Classic with us!
    • By Stan
      Salad Bakers have cleared Naxxramas in WoW Classic under 60 minutes. This is the fastest speed clear of the raid so far. Congratulations!
      Salad Bakers have beaten their own record (1 hour 3 minutes 56 seconds) by a couple of minutes and the guild cleared Naxxramas in 59 minutes and 44 seconds!

      Here's a video of their speed clear. As TehBananaBread pointed out, a boss died every 4 minutes, which is insane!
      Source: Reddit
    • By Starym
      As the Castle Nathria RWF is going on we thought it was time to share the spotlight, as another, equally as impressive and dedicated group of players has taken down the antagonist of many low level players. You can see top level raid leading, the tactics and strategies below, as things get very hairy at the end, with all cooldowns popped and the tank having to kite!
      Unfortunately for the pro group above, this isn't the World First, as it's actually been done before - by a single player:
      Whether this is "end of expansion" type activity or just some usual clean fun, it's always great to see players just doing their own thing and finding their own fun in WoW!
    • By Starym
      After the recent survey that went out and talked about interest in the Burning Crusade Classic, we now have a fairly reliable source talking about more news on the much expected continuation of Classic coming before the end of the year!
      Nano, formerly a core staff member of the Nostalrius private server team, who had a meeting with Blizzard about how they made their server while Vanilla Classic was being developed, tweeted this yesterday:
      While he may theoretically have been referring to the survey, the tweet was posted significantly after it, so it seems more likely this is related to an actual official confirmation/announcement, especially since it refers to a schedule specifically. This comes after Nano correctly predicted/leaked the release schedule for Naxxramas, but also had a time set for the TBC Classic beta in said earlier leak:
      So this source has been pretty reliable in the past, and this tweet sure makes it sound like we won't have to wait for BlizzConline to hear about the Burning Crusade coming to Classic!
    • By Starym
      Blizzard have timed their releases very tightly, as Classic Naxxramas also seems to hold/produce a river of souls of its own... however a very different one than the Shadowlands Maw version. In both cases souls are going to their doom, although in Classic at least they get to have their bodies back!

      Source.

      Source.
      Just in case you're not quite sure what you're looking at, that's a whoole lot of players running back to the raid after death, in a very organized fashion, and it really does look like, and to some extent is, a river of souls.
      And here's the real one from the Maw for comparison:

      (Image courtesy of Warcraft Radio)

      Interestingly, none of the souls in retail seem to be screaming about having to go back to Naxx and the Four Horsemen.
×
×
  • Create New...