lua error
KirbyV2 opened this issue ยท 1 comments
Message: Interface\FrameXML\UnitFrame.lua:458: Usage: GameTooltip:SetUnit("unit"[, hideStatus])
Time: Sun Aug 2 17:42:12 2020
Count: 1
Stack: Interface\FrameXML\UnitFrame.lua:458: Usage: GameTooltip:SetUnit("unit"[, hideStatus])
[string "=[C]"]: in function SetUnit' [string "@Interface\FrameXML\UnitFrame.lua"]:458: in function UnitFrame_UpdateTooltip'
[string "@interface\FrameXML\UnitFrame.lua"]:448: in function oe' [string "@Interface\AddOns\RaiderIO\core.lua"]:2000: in function <Interface\AddOns\RaiderIO\core.lua:1974> [string "@Interface\AddOns\RaiderIO\core.lua"]:2054: in function <Interface\AddOns\RaiderIO\core.lua:2051> [string "@Interface\AddOns\RaiderIO\core.lua"]:2299: in function ?'
[string "@interface\AddOns\RaiderIO\core.lua"]:3201: in function <Interface\AddOns\RaiderIO\core.lua:3201>
Locals: (*temporary) = GameTooltip {
0 =
ItemTooltip = {
}
SetHyperlink = defined =[C]:-1
SetGuildBankItem = defined =[C]:-1
hasMoney = 1
icon = {
}
MAScaled = 0.700000
TopOverlay = {
}
default = 1
MAMover = TooltipMover {
}
SetLootItem = defined =[C]:-1
SetQuestItem = defined =[C]:-1
numMoneyFrames = 1
SetRecipeReagentItem = defined =[C]:-1
SetBuybackItem = defined =[C]:-1
shoppingTooltips =
}
SetMerchantItem = defined =[C]:-1
SetQuestLogItem = defined =[C]:-1
BottomOverlay = {
}
SetTradePlayerItem = defined =[C]:-1
SetSendMailItem = defined =[C]:-1
updateTooltip = 0.058000
SetInventoryItem = defined =[C]:-1
__tamedCounts = false
comparing = false
SetLootRollItem = defined =[C]:-1
CIMI_tooltipWritten = false
SetBagItem = defined =[C]:-1
needsReset = true
SetInboxItem = defined =[C]:-1
SetTradeTargetItem = defined =[C]:-1
SetCurrencyToken = defined @interface\AddOns\Altoholic\Tooltip.lua:700
SetRecipeResultItem = defined =[C]:-1
}
(*temporary) = nil
(*temporary) = nil
It looks like an unit was attempted to be set (when the tooltip was being updated) but there was no unit and it all crashed. Makes sense. Now since we did update the whole code base recently, we just have to assume that this was fixed in that upgrade, but do let me know if this happens again with the latest version. Thanks for the report.