Argent Tournament
a268-Beefy opened this issue ยท 2 comments
Happen during Argent Tornament mount battles
9 0 2 11
1x ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:470: Action[FrameMeasurement] failed because[Can't measure restricted regions]: attempted from: :GetLeft().
[string "=[C]"]: in function GetLeft' [string "@Blizzard_NamePlates\Blizzard_NamePlates.lua"]:470: in function GetPreferredInsets'
[string "@Blizzard_NamePlates\Blizzard_NamePlates.lua"]:166: in function UpdateInsetsForType' [string "@Blizzard_NamePlates\Blizzard_NamePlates.lua"]:150: in function ApplyFrameOptions'
[string "@Blizzard_NamePlates\Blizzard_NamePlates.lua"]:116: in function `OnNamePlateAdded'
[string "@Blizzard_NamePlates\Blizzard_NamePlates.lua"]:56: in function <...eBlizzard_NamePlates\Blizzard_NamePlates.lua:47>
Locals:
(*temporary) = {
otherHealPrediction = {
}
overAbsorbGlow = {
}
myHealAbsorbLeftShadow = {
}
border = {
}
barTexture = {
}
totalAbsorb = {
}
myHealAbsorb = {
}
myHealPrediction = {
}
myHealAbsorbRightShadow = {
}
0 =
background = {
}
overHealAbsorbGlow = {
}
totalAbsorbOverlay = {
}
}
This is something that's happening in the normal blizzard nameplates most likely because some addon, not necessarily Neatplates, has tainted the normal nameplate frame by modifying something that it shouldn't have.
This is something that's been reported before but I've never been able to replicate it when only running Neatplates. Which is why I can't say for sure if it is caused by Neatplates or not.
Edit: While looking into this again, I stumbled across someone that had this issue happen when no addons were enabled. Which is interesting, and makes me further skeptical that this issue is caused by Neatplates. Some people recommended deleting your cache folder World of Warcraft\_retail_\cache if it was happening a lot.