PTR 6.2.2 Nameplate changes

[Blazeflack]

The nameplates have received some updates on the PTR recently.

From this thread you had the following code:

    --full nameplate objects
        local f = NamePlate1 --nameplateframe
        f.barFrame, f.nameFrame = f:GetChildren()
        f.barFrame.threat, f.barFrame.border, f.barFrame.highlight, f.barFrame.level, f.barFrame.boss, f.barFrame.raid, f.barFrame.dragon = f.barFrame:GetRegions()
        f.nameFrame.name = f.nameFrame:GetRegions()
        f.barFrame.healthbar, f.barFrame.castbar = f.barFrame:GetChildren()
        f.barFrame.healthbar.texture =  f.barFrame.healthbar:GetRegions()
        f.barFrame.castbar.texture, f.barFrame.castbar.border, f.barFrame.castbar.shield, f.barFrame.castbar.icon =  f.barFrame.castbar:GetRegions()

The folllowing line will need to be changed if you want to stick with this code:

f.barFrame.healthbar, f.barFrame.castbar = f.barFrame:GetChildren()

to this:

f.barFrame.healthbar, f.barFrame.absorbBar, f.barFrame.castbar = f.barFrame:GetChildren()

In addition to the above change, almost all elements have received parentKeys.
You can now use the following code instead:

local frame = NamePlate1

frame.name = frame.NameContainer.NameText
frame.border = frame.ArtContainer.Border
frame.highlight = frame.ArtContainer.Highlight
frame.level = frame.ArtContainer.LevelText
frame.raidIcon = frame.ArtContainer.RaidTargetIcon
frame.eliteIcon = frame.ArtContainer.EliteIcon
frame.threat = frame.ArtContainer.AggroWarningTexture
frame.bossIcon = frame.ArtContainer.HighLevelIcon

frame.healthBar = frame.ArtContainer.HealthBar
frame.healthBar.texture = frame.healthBar:GetRegions() --No parentKey, yet?
--Available child element (texture): frame.healthBar.OverAbsorb

frame.absorbBar = frame.ArtContainer.AbsorbBar
frame.absorbBar.region1 = frame.absorbBar:GetRegions() --No parentKey, yet? Not sure what region1 is, probably texture like the others.
frame.absorbBar.overlay = frame.absorbBar.Overlay

frame.castBar = frame.ArtContainer.CastBar
frame.castBar.texture = frame.castBar:GetRegions() --No parentKey, yet?
frame.castBar.border = frame.ArtContainer.CastBarBorder
frame.castBar.icon = frame.ArtContainer.CastBarSpellIcon
frame.castBar.shield = frame.ArtContainer.CastBarFrameShield
frame.castBar.name = frame.ArtContainer.CastBarText
frame.castBar.shadow = frame.ArtContainer.CastBarTextBG

Edit: "OnValueChangd" for healthbars now returns values between 0 and 1. Hopefully this is unintended, as it will make it hard to get exact values for nameplates.

[semlar]

Interesting, this should make it simpler to identify the various nameplate regions.

[Blazeflack]

It would appear the "OnValueChanged" script on the nameplate healthbars has been changed as well.

It now returns values between 0 and 1, both included.

[Supernex]

Which file is this in?

[Blazeflack]

Originally Posted by Supernex Which file is this in?

There is no file. It was manually discovered on the PTR.

[Taet]

I please you , anyone who knows how , he could update infinityplate ?

[Resike]

Originally Posted by Taet I please you , anyone who knows how , he could update infinityplate ?

You can download a fan update here:

http://www.wowinterface.com/download...19881#comments

[Resike]

Anyone figured out how to porperly show health values and health max values with nameplates now?

[Blazeflack]

Originally Posted by Resike Anyone figured out how to porperly show health values and health max values with nameplates now?

The only way is to use the UnitHealthMax API when you mouse over a nameplate, then cache that value so you can use it later. Multiply the return from healthBar:GetValue() with the cached MaxHealth to get a guesstimate of the current exact health value.

This will obviously lead to examples where the exact value isn't 100% correct, as a player could receive or lose a health buff right after you cached his MaxHealth. In that case you would need to mouse over that player once more to grab the new MaxHealth.

Suffice to say, the current implementation is not ideal. Hopefully Blizzard will correct it sooner rather than later (and preferrably sooner than Soon™)

[Resike]

Originally Posted by Blazeflack The only way is to use the UnitHealthMax API when you mouse over a nameplate, then cache that value so you can use it later. Multiply the return from healthBar:GetValue() with the cached MaxHealth to get a guesstimate of the current exact health value. This will obviously lead to examples where the exact value isn't 100% correct, as a player could receive or lose a health buff right after you cached his MaxHealth. In that case you would need to mouse over that player once more to grab the new MaxHealth. Suffice to say, the current implementation is not ideal. Hopefully Blizzard will correct it sooner rather than later (and preferrably sooner than Soon™)

This is retarded. Why the heck they had to do this? How hard is it to calculate the percentages by themselfs?

[p3lim]

Originally Posted by Resike This is retarded. Why the heck they had to do this? How hard is it to calculate the percentages by themselfs?

If all you're after is getting percentages, you can do this:

local perc = hpBar:GetValue() * 100
someHealthText:SetFormattedText('%.1f%%', perc)

And use HookScript on the health bar's OnValueChanged and OnShow to update it.

[Resike]

Originally Posted by p3lim If all you're after is getting percentages, you can do this: local perc = hpBar:GetValue() * 100 someHealthText:SetFormattedText('%.1f%%', perc) And use HookScript on the health bar's OnValueChanged and OnShow to update it.

Thats not really the issue, the old percentage functions should work fine even unchanged. The real issue here they probably made the change since the default name plates only show percentages, so better to remove any other usefull information about it.

[Blazeflack]

The health value issue will be fixed in a future update: https://twitter.com/WarcraftDevs/sta...20808857403392

[Resike]

Originally Posted by Blazeflack The health value issue will be fixed in a future update: https://twitter.com/WarcraftDevs/sta...20808857403392

Nice, but i don't get it why can't they just hotfix it in a wednesday maintenance.

[p3lim]

Originally Posted by Resike Nice, but i don't get it why can't they just hotfix it in a wednesday maintenance.

All UI changes require a patch.

[Spyro]

Can we catch nameplates now using if Frame.ArtContainer instead of if Frame:GetName() and Frame:GetName():find("NamePlate") ? Or are there any other children of the WorldFrame with also an "ArtContainer" member?

[Blazeflack]

Originally Posted by Spyro Can we catch nameplates now using if Frame.ArtContainer instead of if Frame:GetName() and Frame:GetName():find("NamePlate") ? Or are there any other children of the WorldFrame with also an "ArtContainer" member?

I don't know if there are other children with that specific element. You would need to test it, but I suspect it might be possible to do it the way you suggest.

Edit: I did a test and only captured Nameplates with the .ArtContainer element.