Jump to content
FORUMS
Sign in to follow this  
Stan

UI API Change for UnitHealth

Recommended Posts

gHn4gFz.jpg

Blizzard has changed the UnitHealth and UnitHealthMax API functions in WoW Classic to return health values for NPCs instead of percentages, meaning you will see how much health a creature has by default without using any addons.

Blizzard LogoBlizzard (Source)

With realm restarts in each region (just completed this morning for Americas realms), we’ve made a change for addons that query unit health.

Now, the UI API functions UnitHealth and UnitHealthMax return health values for NPCs (rather than percentages), information that a very large number of players have been generating with the Real Mob Health addon.

This hotfix has no impact on PVP, as these functions will continue to provide health percentages for enemy players or the units they summon, as before.

Share this post


Link to post
Share on other sites

That's a good change, if you even want to call it that, since it doesn't really change anything. Even the most hardcore no-addons purists in my guild are using Real Mob Health.

Now, if only we could get a proper Threat API... I'm tired of the constant guessing work of whether or not I'm actually ahead in threat or the threat meter just has another hiccup.

Share this post


Link to post
Share on other sites
34 minutes ago, Sabejnos said:

Does it mean that I still have to use an addon to see health points of enemies?

You will need an addon that displays the unit health values in some form. The stock UI doesn't do that, but now you don't need Real Mob Health if you are already using something like Shadowed Unit Frames. If you like the stock UI, you can use Modern TargetFrame.

What this change essentially does is give addon writes direct access to the actual mob health values rather than having to rely on another addons database.

Share this post


Link to post
Share on other sites

Great, now when are they going to allow me to see bars at 40 yards so I don't have to tab target or reduce my range to enemies so I can click like I want to? I mean, seriously Blizzard, why can't I see unit bars at my max range? It is absolutely ridiculous. I understand taking away the ability to see them at 100 yards, but why is it a problem to see them at 40 for max range? It drives me insane.

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 Stan
      Some WoW Classic realms are experiencing long queue times these days and Blizzard revealed they've been working on bringing some relief from the queues to these realms in the near future.
      Firemaw (EU), Incendius (US), and Faerlina (US) currently have extremely long queue times rendering many players unable to join raids unless they log into the game 3 or more hours before raid start.

      Incendius queue times posted by redditor Omgzjustin. [Source]

      Faerlina queue times. [Source]
      Blizzard today said they're working on rolling some changes to reduce the queue times, so either they will offer Free Character Moves from select realms or increase server capacity. More details will be available soon.
      Placeholder for tweet 1246211466266435584
    • By Stan
      Onyxia has been recently defeated in WoW Classic by a raid group comprised of Druids only.
      Reddit user fouronnes and his raid with 32 other Druids have downed Onyxia in WoW Classic.

      Twitch Clip

      Logs
      The raid was able to defeat the boss in a little over 10 minutes. Logs can be accessed by clicking on the image below.

      Source)
    • By Stan
      Queue times return to some WoW Classic realms with a high population amid the coronavirus lockdown and character transfers. Firemaw (EU) players report 3-4 hour queue times on a Sunday, urging Blizzard to lock the realm and a similar situation is occurring on Incendius (US).
      Redditor ANTRagnarok came up with a graph while waiting in the queue and it turns out you must log in at 4:45 p.m. if you want to make it to the raid that begins at 7:30 p.m.

      Players are urging Blizzard to lock Firemaw (EU) on the official forums and offer free character transfers, as many do not want to transfer to different realms using the paid character service.
      The situation was apparently worse the day before with queues exceeding 3,000 players which resulted in 5-6 hour queue times. Redditor Aoussar123 reports that people are idling in cities hitting the space bar every once in a while to stay logged in which makes things even worse.

      Incendius (US) is facing a similar situation, but the queues aren't as bad as in Europe. The realm was beyond capacity full even before paid character services, then came transfers from Faerlina, Skeram, and other realms, rendering Indencius beyond unplayable according to Redditors. Players reported 2-3 hour queue times on Incendius during raid time.
      Blizzard has so far not responded to any of the reports and we will keep you updated should they come up with any solutions in the near future.
    • By Stan
      UPDATE: The issue has now been resolved.
      Blizzard (Source)
      The aforementioned fix was completed with restarts at 6:00 a.m. AEDT, and the Battleground Holiday has been operating as expected on Oceanic realms since then. The first Battleground Holiday has been delayed in Oceania due to a bug. Blizzard is currently working on a fix that may require Classic realm restarts.
      Blizzard (Source)
      The first Battleground Holiday should have gotten underway on Oceanic realms at 12:01 a.m. AEDT (about 4.5 hours ago). That has not yet happened, due to a bug.
      We’re working on a fix, and the fix may require realm restarts of Oceanic Realms, which we would undertake very soon if necessary.
      We apologize for the delay.
    • By Stan
      Blizzard today announced they suspended numerous WoW Classic players that were found to be using anti-AFK cheats or bots that automated movement, mainly in Alterac Valley.
      Anything that degrades the gaming experience for other players will result in harsh penalties, according to Blizzard, and they will continue to issue suspensions based on player reports, so if you see someone circumvent AFK rules, make sure to report them!
      Blizzard (Source)
      Yesterday, we issued numerous suspensions to WoW accounts that were found to be violating our Code of Conduct. Affected players were e-mailed with details about the violation and suspension – a great many of which were found to be using anti-AFK cheats or bots that automate movement, especially in Alterac Valley.
      This was the most-recent in a series of similar actions we’ve taken to address unfair gameplay in WoW Classic.
      Please be reminded that using third-party programs to automate any facet of the game, exploiting bugs, or engaging in any activity that grants an unfair advantage is considered cheating. Exploiting other players is an equally serious offense. Scamming, account sharing, win-trading, and anything else that may degrade the gaming experience for other players will receive harsh penalties.
      We’ll continue to monitor reports of and take actions against players who circumvent AFK rules. If you come across a player violating the Code of Conduct policies, please report them.
      Thank you.
×
×
  • Create New...