Jump to content
FORUMS
Sign in to follow this  
Stan

Diamond Flask & Nightfall Working As Intended in WoW Classic

Recommended Posts

45100-avoid-streamers-in-wow-classic.jpg

The behavior of Diamond Flask and Nightfall matches WoW 1.12 and the Reference Client, and both items are working as intended in WoW Classic.

Diamond Flask

There have been some reports about Diamond Flask's HP5 snapshots on the official forums, but Blizzard confirmed the item is working as it did back then, and there are no plans to change it.

Blizzard Logo(Source)

Greetings!

We’ve looked into these reports and have found that the Diamond Flask’s behavior does in fact correctly match Original WoW 1.12 as well as the Reference Client. For now, at least, we have no plans to change it.

As we do not consider this to be a “bug”, I’m going to be closing this thread now. Thank you!

Nightfall

Blizzard also thoroughly tested NightfallNightfall and found out that the item is behaving as expected too. More details can be found in the blue post below.

Blizzard Logo(Source)

Greetings!

We’ve spent a significant amount of time digging into the claims in this thread and at this time we can conclude that NightfallNightfall is in fact behaving as expected.

To respond to specific claims or theories in this thread, here’s a very quick outline of what we found:

  • NightfallNightfall can and does proc from glancing blows.
  • NightfallNightfall can and does proc from white hits or yellow hits.
  • NightfallNightfall is refreshed if the same player procs it twice within the 5-sec duration, but it is removed & re-applied if it is procced by a second player during the first player’s NightfallNightfall effect.
  • NightfallNightfall can be applied from front & behind.
  • If there are two players with NightfallNightfall, it has approximately double the uptime as when only one is present. (A little less than, simply due to it being more frequent for player B to overwrite player A when both are attacking, than player A overwriting themselves when they are attacking alone.)
  • The NightfallNightfall proc effect is considered physical and cannot be resisted. No resists are even being attempted in the combat rolls.
  • Over dozens of 5-minute “target dummy” tests against level 63 Boss mobs, we found that the effect had a roughly 8-13% total proc rate, which is well within expectations for a 3.5 speed weapon with a PPM of 2 (~11.6% raw proc-per-hit).
  • Even in our higher percentage data sets (where we observed proc rates of 13% or more over 5 minutes) we at times went as much as a full minute between procs.

It’s important to understand there is no “bad luck protection” or other normalization for procs in Original WoW or WoW Classic. Its quite possible (and common) to go extended periods of time with no procs, or to have multiple back-to-back procs. You are especially susceptible to not seeing consistent procs when bosses die very quickly, or if there is a lot of movement or other mechanics that prevent constant uptime on bosses (The Chromaggus run-in, run-out “dance” is a good example of this).

I’m going to go ahead and close this thread now as well, since we’ve determined that this item is working as expected. We very much appreciate the observations and analysis that everyone has provided for this.

Thank you!

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 Starym
      The mono-class raids are back in full swing it seems, after yesterday's (almost) all mage Ny'alotha, except this time it's on Classic (and there's not that 1 Demon Hunter a lot of the other "mono" raids tend to use, which would be somewhat difficult to pull of in Classic anyway). Хасу (Hasu), GM of <Нам Везёт Мы Играем> took 39 more shamans into Ragnaros' lair and came out victorious!
      The full clear took them around 3 hours, with the DPS consisting of mostly elemental specs, the tank obviously being enhancement, and the fights starting at 8 restos and ending at 12 at Majordomo and Rag.
      Here's the full Ragnaros run, and you can check out the rest of the raid by skipping through the VoD. Enjoy the FULL RP section, in Russian, because I'm feeling cranky!

      And here are some comments from one of the raiders, from before the run took place:
      Source.
      And here's another shaman art piece by Peter Lee, because Tauren shaman > all! And also because I couldn't find the author (D.H.) of the header image to source it.

    • By Stan
      Blizzard has enabled a second layer for Herod and Whitemane in the North American region.
      (Source)
      Over the next few minutes, we’re enabling a second layer for the Herod and Whitemane realms. This is a step we’re taking very carefully to make it so that players can enjoy playing on those realms during peak hours.
      It has been a very high priority for us to understand why, after we de-layered ten realms on May 14, these two realms reversed course and experienced this, while the others did not. We will continue to pay very close attention to this situation and make adjustments to the game service as necessary.
      As before, Herod and Whitemane remain restricted from the Character Transfer service.
    • By Starym
      We have some crazy pulls today as both a mage and a paladin have been doing some massive mob gatherings over in Sunken Temple, downing almost all the dungeon's mobs in 1 pull (with around 100 elites for the mage and 72 for the paladin. First off we have Taiwaneseninja using the mage's frost spells to control the pull and get pretty much all the dragonkin and trolls in the temple to 1 location, while using the many ledges/glitch spots to better bunch the mobs up (and manage to use a bandage or two).
      But that wasn't quite enough for the mage, as he decided to get some nature resist gear and head back in for a faster clear time:
      Then we have the same principle, but a paladin has to be a bit less enthusiastic, since he can "only" manage all of the dragonkin at once, and also has to rely on some engineering bombs to get the job done (he also explains how to get some non-engineer bombs in the video/description as well).
      Both of the players have been optimizing this for boosting purposes, with 1-3 other players just sitting at the entrance and getting quite a bit of XP.
      Source.
    • By Stan
      Blizzard posted an updated list of Classic realms that are restricted from character transfers. These include Faerlina, Herod, Pagle, Sulfuras, Whitemane, Golemagg, Sulfuron, and other realms.
      (Source)
      At this time, the following realms are temporarily restricted from character transfers. You cannot purchase a Paid Character Transfer to:
      NA Realms
      Realm Locale Type Arugal Oceanic PvP Benediction Eastern PvP Earthfury Eastern PvP Faerlina Eastern PvP Fairbanks Pacific PvP Grobbulus Pacific RP-PvP Herod Eastern PvP Pagle Eastern Normal Sulfuras Eastern PvP Whitemane Pacific PvP EU Realms
      Realm Locale Type Ashbringer English PvP Auberdine French Normal Firemaw English PvP Flamegor Russian PvP Gehennas English PvP Golemagg English PvP Mograine English PvP Sulfuron French PvP Venoxis German PvP Zandalar Tribe English RP-PVP Restrictions may be added or lifted as necessary at any time, without warning.
      As always, we suggest that players who wish to avoid queues on the most popular realms select a different realm than those listed above.
    • By Stan
      Blizzard is working on a series of hotfixes that they hope to release in the next few days. First, they are increasing the spawn rate of Black Lotus. The second hotfix affects some Warsong Gulch places that should not be accessed by players. The final hotfix tags you as busy if someone else tries to start a trade with you if you are engaged with the mailbox or bank.
      (Source)
      Via hotfixes, we’re working on several quality-of-life improvements that should go live in the next few days.
      Black Lotus scarcity has been consistently among the top issues we’ve seen player feedback about, so we’ve decided to update how we handle Black Lotus spawns. Since the launch of WoW Classic, the game has used the spawn times and locations from original World of Warcraft, but population and social factors have led to Black Lotus being much more scarce than it was in original WoW. While these issues affect all mining and herb nodes to some degree, Black Lotus is especially affected because it has the special property of only having one spawn up at a time in each of the zones it spawns in.
      In original WoW, designers planned Black Lotus around a technical limitation – only 10 spawn locations per node type could be active at the same time in the same zone. We no longer have that limitation, but it gives us a design intention that we can work with: Black Lotus was supposed to spawn in the widest variety of locations, while there could only be one up at a time in each zone. As always, our goal is to minimize differences from original World of Warcraft, and we feel this is a case where we can follow that design intention in a way that is warranted by modern conditions as well as beneficial to players.
      We’re going to increase the spawn rate of Black Lotus, and we’re going to add many additional possible spawn locations in each of the Black Lotus zones. With a different hotfix, we’re working on making it so that a player cannot see a Black Lotus on-screen or on their minimap if they’re dead, unless they have 300 Herbalism.
      For Warsong Gulch, we’ve identified a number of locations in the battleground where clever players have found ways to get to a place they were never intended to go. These exploits are decidedly unfair, so we’re putting a stop to them. In most cases, the way we prevent such things is to place an invisible gate that blocks the unintended path. However, that’s sometimes impossible, so we make the out-of-bounds location fatal.
      We’re also working on a hotfix that should put a stop to one small annoyance – now, if a player is actively engaged with the mailbox or bank, they will be considered “busy” if someone else tries to initiate a trade with them.
      We’ll have all of these changes noted for you in the next Hotfixes Update that follows them going live.
×
×
  • Create New...