Threat Plates

Threat Plates

31M Downloads

Weird tooltip bug after 10.0.2

Nillx opened this issue ยท 13 comments

commented

Since wow update 10.0.2 i started seeing stuff like this.
202316616-208cf367-3f20-4fb0-afce-51cca3aa6c23
202311102-b626d5b6-d3bf-4a84-9e0e-5caddb74e1b1
202183516-1eb7ebc6-d365-4334-b211-fff8470d0a20

At first i thought it was a Leatrix Plus issue but then i noticed that its happening with Rarity as well. This is happening only when Threat Plates is enabled.

Was able to reproduce it in different locations. Noticed that its often happening when there is an active name plate on the screen. Go in a place with a lot of enemy NPCs and start turning around your camera while targeting yourself, then check the tooltip if you have an addon that shows the target (Like Leatrix Plus).

commented

Not sure why that should be happening. Threat Plates does not really modify tooltips except creating aura tooltips (which the above is not). Hm ...

commented

I will look into https://wowpedia.fandom.com/wiki/Patch_10.0.2/API_changes#Tooltip_Changes - maybe, my best guess currently, it is related to these changes.

commented

I really wish i was able to help

commented

For me, it's always okay if I at least can reproduce the bug and then have an idea why a bug is occuring. So, this is fine here. There are other issues where I am completely lost why they happen. That is what is really frustrating ...

commented

Does the following version fix the issue for you: https://drive.google.com/file/d/1vrX5RVJg3fMMoYydM-C00BthldhN2EIm/view?usp=sharing

I re-worked all tooltip code (using in status text and Quest widget). There is still some tooltip code in the libraries (e.g., Ace3), but that hopefully is not the reason for the above bug.

commented

For now im not seeing that issue with this version. Will post again if i see it happen again.

commented

I'm seeing this issue and I don't use Threat Plates, so it may be a lib or a core game issue.

commented

Interesting, it was happening only when TP is enabled and there are nameplates on the screen but its a bit difficult to reproduce so maybe i missed it.

commented

Threat Plates has embedded some libraries, e.g., Ace3. If the error is on one of these libs, then they would occur even when only TP is enabled. I think I will check these addons as well.

I know that there is an updated (alpha) version of Ace3 which changed some tooltip code, but I still cannot believe that this wuold be the cause of this bug.

commented

If it helps, I am getting this trace
v11.1.2

756x SharedXML/Tooltip/TooltipUtil.lua:8: attempt to index local 'tbl' (a nil value)
[string "@SharedXML/Tooltip/TooltipUtil.lua"]:8: in function <SharedXML/Tooltip/TooltipUtil.lua:7>
[string "@TidyPlates_ThreatPlates/Functions/healthtext.lua"]:90: in function <...Ons/TidyPlates_ThreatPlates/Functions/healthtext.lua:77>
[string "@TidyPlates_ThreatPlates/Functions/healthtext.lua"]:227: in function `func'
[string "@TidyPlates_ThreatPlates/Functions/healthtext.lua"]:329: in function `SetCustomText'
[string "@TidyPlates_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua"]:851: in function <...s_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua:845>
[string "@TidyPlates_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua"]:406: in function <...s_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua:376>
[string "@TidyPlates_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua"]:467: in function <...s_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua:445>
[string "@TidyPlates_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua"]:1127: in function `?'
[string "@TidyPlates_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua"]:1081: in function <...s_ThreatPlates/TidyPlatesInternal/TidyPlatesCore.lua:1080>

Locals:
tbl = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index local 'tbl' (a nil value)"
commented

Does this happen on Retail or on Classic?

commented

Sorry for late reply, it happened on retail.

commented

Fixed with release 11.1.2 - I never saw this again after that.