Modern TargetFrame adds features present in Modern WoW.
- StatusBar text for health and mana bars. Formatting is still controlled by Status Text under Interface Options > Display.
- Rare-Elites now show the Rare-Elite TargetFrame border. (Silver dragon with wings, normal rares are without wings)
- Threat indicator with numerical value.
Notes:
- The game identifies many normal elites as rares. I don't plan on modifying this behavior in any way.
- The threat indicator appears to spike whenever the target changes its target, usually by taunts or threat-related mechanics. This is a well-known bug in Blizzard's ThreatAPI.
Localization:
- enUS - Native locale by SDPhantom
- deDE - Translation by xF10w21
- frFR - Translation by Arektor
- ruRU - Translation by AmetistoFF
- zhCN - Translation by 颜颜@莫格莱尼
If you wish to help localize Modern TargetFrame, send me a link to a modified Localization.lua.
Contact:
I'm open to questions and suggestions. Feel free to message me here or post in the comments.
I'm also available for support on the WoWUIDev Discord, @mention me (SDPhantom) or send a DM.
Can you tag your file releases for the BC client version so addon programs can pull it in?
It is tagged, hence the WoW Burning Crusade Classic section in the file listings to the right on the site.
Also, click on the file name and it'll show both 2.5.1 and 1.13.7 tags.
In reply to SDPhantomGamer:
Ah my bad I didn't look deep enough, maybe Ajour is acting up then, thanks!
Could you please add party member class Icon and target class icon?
Not really within the scope of this addon.
I just updated to the latest 1.10.1 version and my Threat Glow seems to be broken (see image below). This was tested without other unit frames addons enabled. Turning the option or addon on & off again didn't fix it either. Is this a problem on my end?
EDIT: Fixed, was a problem on my end & not with the addon. I still had some custom textures installed that caused the issue.
In reply to neverblooom:
heya , wich addon u use for this frame look ? ty
In reply to Khadaf_iZi:
A texture pack called Santa UI Textures (available on wowinterface here https://www.wowinterface.com/downloads/info18608-SantaUITextures.html). If you do decide to use that with this addon, make sure to remove (or rename) the file UI-TargetingFrame-Flash.blp in the "TargetingFrame" folder that comes with the Santa UI Textures. That was what caused the problem I posted above.
In reply to neverblooom:
thank's for the answer & the tips ;)
Hey just downloaded this addon since TBC prepatch broke hp values for me. It works on friendly and enemy NPCs, but it doesn't show player character hp values only percentages still. Can that be fixed as well?
Player/pet values for those outside your party/raid have never been available for classic.
Their percentage display just looks different because of a change Blizzard did to their format function.
In reply to SDPhantomGamer:
I could see accurate hp values of all friendly player characters in classic, even if they were not in my party/raid (after blizz allowed unit health to be known and mobhealth addon was no longer needed). Enemy player characters did however always show percentages only.
Sidenote:
There is a bug that shows up sometimes on the frames that shows visual 1/1 as mob health (presumably the bugged blizzard accurate hp for mobs option) under the addon activated accurate hp. It gets meshed together and the hp is harder to read because of it.
Loaded up both clients, targeted a random player and ran /dump UnitHealthMax("target").
Both Classic and BCC return 100. The only difference between Classic and BCC builds is percentages are shown in a different format. Both versions are formatted by Blizzard, not Modern TargetFrame.
Thanks for fix hp show!
In reply to Visc1n:
is it fixed for you, I don't see hp numerical values yet... only percentage.
There is a setting to apply the patch in the options. I would ask you check your StatusText settings too.
Also health for players and pets outside party/raid are still percents.
Is there any other way to show mob HP in numeric value on default frames? I was using this addon whole classic, thank you very much SDPhantomGamer for that. Now I need a TBC version :D
I'm working out some quirks with the patch, but they're dong maintenance right now. I updated the forum post with a recreation of the bugged function in a working state.
In reply to SDPhantomGamer:
It may not actually be a bug. A few days ago, I tried to find out the truth of back then, if you actually could see health numbers for targets not in your party in TBC, and I kept finding arguments both ways. In the end, it seemed likely that you could not, and while I can't remember with 100% certainty myself, that DOES feel familiar. I'm mostly sure I remember being upset with not being able to see enemy health in TBC and being so relieved (and upset at the devs for holding back so long, showing nothing in Original and then just mere % in TBC) when we finally could in WotLK.
That said, your other addon, PhantomPlates, does show actual health. I assume the addon uses a library like a database of saved health values for every single NPC in the game? I'm not totally sure how addons work, but that sounds feasible. Therefore, couldn't the same exact thing be done with Modern TargetFrame?
However it works, I wonder if that could be considered cheating even if it doesn't really matter? Like I know they're not going to ban anyone for it, that'd be crazy, but just something to ponder. I'm definitely not a "no changes" guy, so regardless of whether it showed or not back then, I'd like it in.
It's a change they made part way into Classic because of something I did. In the beginning of Classic, I made RealMobHealth, an addon that recorded the health of mobs you killed and would share it with other players. The popularity of the addon grew to a state where the comms traffic in order to support this was causing problems with Blizzard servers. Their answer was to stop blocking health values, making the addon obsolete.
This addon along with PhantomPlates split off from RealMobHealth into their own projects with vastly expanded feature sets than just showing health. There's a big difference in how these two addons handle showing health.
Modern TargetFrame actually doesn't handle it at all. In Vanilla Classic, the code responsible for formatting the health text is still running even though it has no text objects to write to. The Classic client was a modified version of the Retail client at the time, Legion 7.3. All Modern TargetFrame did was put the text objects Blizzard removed back in their place and everything started working as it did in the Retail version. This is more or less the same way it's handled in TBC Classic, only Blizzard put the text objects back in themselves and Modern TargetFrame no longer had to deal with that.
The difference with PhantomPlates is because NamePlates never had health text in either client. Because of this, there is no already-existing format function. It's all custom code that asks the game what the health value is and displays it.
The issue now is that Blizzard added a new function to help control how its formatter displays health. The problem is the behavior of this function is inconsistent with actual health visibility. This is why there's a perceived difference between Modern TargetFrame and PhantomPlates right now. Blizzard's formatter is saying it doesn't have health data while PhantomPlates just shows the values that the game gave it without a care. This is also probably why most UnitFrame replacements and custom UIs aren't affected by this. They bypass Blizzard's format function entirely.
PS: If you want to read more about the UnitHealth changes, here's the forum thread.
https://us.forums.blizzard.com/en/wow/t/wow-classic-ui-api-change-for-unithealth/446596