If you used Edit Mode even in a fresh login, clicking on Quest Tracker after getting in and out of combat gives this error.
4x [ADDON_ACTION_BLOCKED] AddOn 'AzeriteUI' tried to call the protected function 'ObjectiveTrackerFrame:SetPointBase()'. [string "@!BugGrabber/BugGrabber.lua"]:485: in function <!BugGrabber/BugGrabber.lua:485> [string "=[C]"]: in functionSetPointBase'
[string "@FrameXML/EditModeSystemTemplates.lua"]:138: in function SetPoint' [string "@SharedXML/LayoutFrame.lua"]:290: in functionLayoutChildren'
[string "@SharedXML/LayoutFrame.lua"]:225: in function Layout' [string "@FrameXML/UIParent.lua"]:3215: in functionUIParentManageFramePositions'
[string "@FrameXML/UIParent.lua"]:2685: in function <FrameXML/UIParent.lua:2672>
string "=[C]": in function SetAttribute' [string "@FrameXML/UIParent.lua"]:3232: in functionUIParent_ManageFramePositions'
[string "@Blizzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua"]:1508: in function <...zzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua:1401>
string "=[C]": in function `ObjectiveTracker_Update'
[string "@Blizzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua"]:995: in function <...zzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua:897>
Locals:
_ = Frame {
RegisterEvent = defined @!BugGrabber/BugGrabber.lua:491
0 =
UnregisterEvent = defined @!BugGrabber/BugGrabber.lua:491
SetScript = defined @!BugGrabber/BugGrabber.lua:491
}
event = "ADDON_ACTION_BLOCKED"
events =
{
ADDON_ACTION_BLOCKED = defined @!BugGrabber/BugGrabber.lua:557
ADDON_ACTION_FORBIDDEN = defined @!BugGrabber/BugGrabber.lua:557
PLAYER_LOGIN = defined @!BugGrabber/BugGrabber.lua:551
LUA_WARNING = defined @!BugGrabber/BugGrabber.lua:566
ADDON_LOADED = defined @!BugGrabber/BugGrabber.lua:511
}
`
To reproduce
Use Edit Mode and quit it. No need to change anything.
Get in combat and get out of combat.
Click quest tracker.
Expected behavior
It should not give any error when you are out of combat.
Screenshots
No response
Additional context
It's a niche situation and not necessarily needs a fix but it's happening. Using default Quest Tracker skin and/or disabling Explorer Mode makes no difference.
Game Flavor
Dragonflight
Is there an existing issue for this?
Describe the bug
If you used Edit Mode even in a fresh login, clicking on Quest Tracker after getting in and out of combat gives this error.
4x [ADDON_ACTION_BLOCKED] AddOn 'AzeriteUI' tried to call the protected function 'ObjectiveTrackerFrame:SetPointBase()'. [string "@!BugGrabber/BugGrabber.lua"]:485: in function <!BugGrabber/BugGrabber.lua:485> [string "=[C]"]: in function
SetPointBase' [string "@FrameXML/EditModeSystemTemplates.lua"]:138: in functionSetPoint' [string "@SharedXML/LayoutFrame.lua"]:290: in function
LayoutChildren' [string "@SharedXML/LayoutFrame.lua"]:225: in functionLayout' [string "@FrameXML/UIParent.lua"]:3215: in function
UIParentManageFramePositions' [string "@FrameXML/UIParent.lua"]:2685: in function <FrameXML/UIParent.lua:2672> string "=[C]": in functionSetAttribute' [string "@FrameXML/UIParent.lua"]:3232: in function
UIParent_ManageFramePositions' [string "@Blizzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua"]:1508: in function <...zzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua:1401>string "=[C]": in function `ObjectiveTracker_Update' [string "@Blizzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua"]:995: in function <...zzard_ObjectiveTracker/Blizzard_ObjectiveTracker.lua:897>
Locals: _ = Frame { RegisterEvent = defined @!BugGrabber/BugGrabber.lua:491
0 =
UnregisterEvent = defined @!BugGrabber/BugGrabber.lua:491
SetScript = defined @!BugGrabber/BugGrabber.lua:491
}
event = "ADDON_ACTION_BLOCKED"
events = {
ADDON_ACTION_BLOCKED = defined @!BugGrabber/BugGrabber.lua:557
ADDON_ACTION_FORBIDDEN = defined @!BugGrabber/BugGrabber.lua:557
PLAYER_LOGIN = defined @!BugGrabber/BugGrabber.lua:551
LUA_WARNING = defined @!BugGrabber/BugGrabber.lua:566
ADDON_LOADED = defined @!BugGrabber/BugGrabber.lua:511
}
`
- © Githubissues.
- Githubissues is a development platform for aggregating issues.
To reproduce
Use Edit Mode and quit it. No need to change anything. Get in combat and get out of combat. Click quest tracker.
Expected behavior
It should not give any error when you are out of combat.
Screenshots
No response
Additional context
It's a niche situation and not necessarily needs a fix but it's happening. Using default Quest Tracker skin and/or disabling Explorer Mode makes no difference.