Neuron

Neuron

98.2k Downloads

Lua errors, spell ids/tooltips

teh-fixerer opened this issue ยท 7 comments

commented

Hi,
Getting some lua errors even after recent update on a few characters, especially hunter. Call pet spell placed on the action bar seem to be the cause. Had some on my fury warrior too, but it was a button that got copied over from the other spec (arms) will check into it more and post separately if I can.

Message: Interface\AddOns\Neuron\Neuron_Buttons.lua:2230: Invalid spell ID in GameTooltip:SetSpellByID
Time: 01/16/18 20:08:05
Count: 16
Stack: Interface\AddOns\Neuron\Neuron_Buttons.lua:2230: Invalid spell ID in GameTooltip:SetSpellByID
[C]: ?
[C]: in function SetSpellByID' Interface\AddOns\Neuron\Neuron_Buttons.lua:2230: in function MACRO_SetSpellTooltip'
Interface\AddOns\Neuron\Neuron_Buttons.lua:2310: in function `MACRO_SetTooltip'
Interface\AddOns\Neuron\Neuron_Buttons.lua:2352: in function <Interface\AddOns\Neuron\Neuron_Buttons.lua:2337>
[C]: ?

Locals:

commented

it disappeared for a while when blizz pushed a small patch, but it is back now?

commented

Is it just this single ability causing the bug, or do others trip the error as well?

commented

So far it is just the hunter call pet spells that cause it. I put a button for each pet pet on my bar.
If you don't have an active pet, everything is fine, tooltips and icons as normal. Once you summon a pet, the lua errors begin and the icons become "clear"

see before (no active pet) and after (with pet) screen grabs below:

wowscrnshot_011718_104541
wowscrnshot_011718_104605

commented

Not sure how i managed to close the ticket, but the issue is still active.
I don't normally play marks, just survival and beast master, but I'll check on marks and see if i can gather up whats happening there.

commented

Yeah this bug appears to be a new occurance as of 7.3.5. I'll have to log onto my girlfriends hunter to replicate the error and find out what's going on. It's always fun when blizzard changes spellID's and doesn't mention it ;-)

commented

Fixed in the last commit. The fix will be in the next version :-)

commented

Many thanks!