Error on Load in recent update
Closed this issue · 5 comments
Hi, I mostly play Classic Era and noted I'm getting the following error when I log in after the most recent update:
Date: 2025-07-04 09:21:37
ID: 1
Error occured in: Global
Count: 1
Message: ...dOns/TidyPlates_ThreatPlates/Widgets/QuestWidget.lua line 147:
attempt to index local 'RegexpForExpansion' (a nil value)
Debug:
[C]: ?
[Interface/AddOns/TidyPlates_ThreatPlates/Widgets/QuestWidget.lua]:147: in main chunk
From the looks of the code, it is trying to index the following table:
-- Since patch 8.3, quest tooltips have a different format depending on the localization, it seems
-- at least for kill quests
-- In Shadowlands, it seems that the format is randomly changed, at least for German, so check for
-- everything as a backup
local OBJECTIVE_PARSER_REGEXP_BY_EXPANSION = {
[LE_EXPANSION_MISTS_OF_PANDARIA] = {
-- Format (Mists): " - Objective: x/y"
LEFT = "^%s.%s(.*: )(%d+)/(%d+)$",
RIGHT = "^%s.%s(.*: )(%d+)/(%d+)$",
},
MAINLINE = {
-- Format: "x/y Objective"
LEFT = "^(%d+)/(%d+)( .*)$",
-- Format: "Objective: x/y"
RIGHT = "^(.*: )(%d+)/(%d+)$",
},
}
In the line local RegexpForExpansion = OBJECTIVE_PARSER_REGEXP_BY_EXPANSION[Addon.GetExpansionLevel()], however on testing this call to GetExpansionLevel() is returning a number, 0 for Classic Era, and 4 for MoP, and 10 for Retail. None of these numbers seem to be valid values to reference into the regex table though, although I could be wrong, as it's tricky to navigate to where some of these values might be defined. I feel there's some conversion step missing here, but not sure what was intended?
Just wanted to bring it to your attention.
The issue here is that the Quest widget is disabled in Classic as now Quest tooltips are available. But I did not disable it correctly or completely (while working on enabling it for Mists Classic). That's why this Lua error is thrown.
I will upload a fixed version in a few minutes. Thanks for reporting this.
You're welcome. Thanks for the update on what's going on. It's interesting to have a poke and learn about this stuff.
New version 12.3.4 is just being uploaded and should be available in a few minutes. The error should be gone after installing it.