Describe the bug

Opening a quest and mousing over Mark of the World Tree for Hyjal 2 errors come up. Not sure about other currencies, I just came over to redo this questline.

Steps to Reproduce

Close error and mouse over currency earned for quest, in this case again Mark of the World Tree, I circled in red the item I mouse over to get this to happen

Expected behavior

None

Additional context

First Lua error

Message: Interface/AddOns/TipTacItemRef/ttItemRef.lua:921: attempt to call global 'GetQuestCurrencyInfo' (a nil value)
Time: Mon Jul 29 19:29:56 2024
Count: 3
Stack: Interface/AddOns/TipTacItemRef/ttItemRef.lua:921: attempt to call global 'GetQuestCurrencyInfo' (a nil value)
[string "=[C]"]: in function GetQuestCurrencyInfo' [string "@Interface/AddOns/TipTacItemRef/ttItemRef.lua"]:921: in function <Interface/AddOns/TipTacItemRef/ttItemRef.lua:918> [string "=[C]"]: in function SetQuestCurrency'
[string "@Interface/AddOns/Blizzard_UIPanels_Game/Mainline/QuestInfo.lua"]:1250: in function <...AddOns/Blizzard_UIPanels_Game/Mainline/QuestInfo.lua:1229>

Locals:

Second error

Message: Interface/AddOns/TipTacItemRef/ttItemRef.lua:921: attempt to call global 'GetQuestCurrencyInfo' (a nil value)
Time: Mon Jul 29 19:32:42 2024
Count: 6
Stack: Interface/AddOns/TipTacItemRef/ttItemRef.lua:921: attempt to call global 'GetQuestCurrencyInfo' (a nil value)
[string "=[C]"]: in function GetQuestCurrencyInfo' [string "@Interface/AddOns/TipTacItemRef/ttItemRef.lua"]:921: in function <Interface/AddOns/TipTacItemRef/ttItemRef.lua:918> [string "=[C]"]: in function SetQuestCurrency'
[string "@Interface/AddOns/Blizzard_UIPanels_Game/Mainline/QuestInfo.lua"]:1250: in function `UpdateTooltip'
[string "@Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua"]:421: in function <...AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua:414>
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: ?

Locals:

Version of TipTac Reborn

v24.07.28-release

Flavor/Version of WoW

Retail

Thanks for reporting this! 👍

Will be fixed with the next release. Duplicate of #319.

OOF, sorry for creating a duplicate post, will keep a sharper eye and post with them
Or is it better to make separate posts
Just love the addon lol

It's good to check if the latest issues already mention the error you encounter. If it's the exact same lua error, then it's normally not necessary to post something additionally, because I'm already on it. If the error is different but belongs to one of the latest issues, then it's good to post your infos there. If it's something new, a new issue needs to be created.

Nevertheless it's good to report problems or feature requests, so that I can improve this addon. 😉