This addon restores the old quest log with the familiar list of quests on the left and details on the right.
This addon's initial behavior is to commandeer your quest log key binding and micro button to toggle the new log. It should be a familiar enough experience once you log in.
If you decide you want to keep using the new default log alongside this addon, you can:
- Open the map via key binding (M is default key) will display the new map+quest log hybrid.
- Click 'Show Map' in the upper right of the Classic Quest Log, it will jump to the map of the quest's zone with the attached new style quest log.
- If that's not enough and you only want to use the Classic Quest Log occasionally, go into Key Bindings -> AddOns -> Classic Quest Log and set a binding to toggle this addon's window. Once a binding is set, it will revert the behavior of the default quest log binding and quest micro button to its map+quest default behavior.
There are a few minor changes from the true old quest log:
- Instead of saying (Completed) or (Daily) beside each quest name, they are now represented by icons just like the new log.
- There are other options in the Options button at the bottom of the window, such as the ability to move the window around the screen or to resize the height of the window.
I'm not sure if it's this addon doing it, but every time I click the quest on the side it opens up both the map and the quest log. Again I'm not sure if it's this addon doing it or not.
In reply to Lovin90:
Thanks for the report. This is kinda bugged. I'll see what I can do.
I went back to 1.4.2 due to the lack of quest log auto-placement when I have another window open. The new version overlaps with other open windows such as Reputation, Character, etc. Since going back I have no issues or bugs related to CQL in my interface. Just adding my 2c in case it helps, as it seems many are disappointed with the new version(s).
EDIT: I also tried to bug it by picking up and completing a quest, and neither event caused any bugs or errors in my game.
In reply to Ceejaikae:
Are you able to open it while in combat?
In reply to gello3:
Sorry for the late response. I just tested, and here are my results. I cannot open nor close the quest window while in combat (unless I click the 'X' to close the window). However, if the quest window is open prior to entering combat, I do not have any issues toggling it or any other windows after combat ends. I understand how this may be frustrating to some, but opening the quest window during combat is not something I generally do, and, thus, I'm pretty ok with the 1.4.2 version for the time being.
I should have added (to begin with) that I also use Kaliel's Tracker as a default quest tracker replacement. I'm not sure if the interactions betwixt the addons are what is causing my lack of issues, but I figured it's good information to put out there regardless.
In reply to Ceejaikae:
Thanks for the info. I'll do some more research on this to see if the option can be revived.
The newest version borks anchoring and is incompatible with ElvUI. It force locks the quest log to center with no ability to re-position to a new locked location.
In reply to Congelatore:
Click the options button and confirm 'Lock Window Position' is not checked. When that's not checked, the window can be moved by dragging the titlebar or most areas of the window that don't intercept mouse clicks. While checked, the window cannot be moved unless Shift is held while dragging.
For the time being, panel-like anchoring is disabled. This is an intentional change due to new protections put on Show/HideUIPanel in the 8.2 patch. The 'Undock Window' option in the addon is forced on and cannot be turned off.
If any other ElvUI users are reading this, are you finding this addon incompatible with ElvUI?
A new update has been posted that should clear up more issues. A more permanent fix (detaching itself completely from the default quest system) is in the works.
In reply to gello3:
Thank you. Works really great, no problems at all :)
In reply to gello3:
i can also confirm i have had 0 errors so far with version 1.4.4 :D, your on the right track ;)
Yeah I've had to disable this addon for now, it completely broke things for me. Not just issues accepting quests, but also opening vendor windows and similar. I hope this can be fixed because I really like this addon.
I appreciate your attempt to fix the errors that happen since the last WoW patch. But the latest version of your addon, 1.4.3, actually made it worse for me. Although 1.4.2 has the problem that I can't open it in combat, at least I never had a single error message with it. But with 1.4.3 I got multiple "SetPoint failed" errors on one day, mostly when I tried to accept a quest (happend from an object in the world, from a NPC and from an automatically accepted quest). I also got the problem that I can't see the quest rewards when the error happens when I talk to a NPC.
It got so bad, that I couldn't prevent the errors, even after multiple tries to reload the UI. So I downgraded to 1.4.2 and now I can accept the quest again without errors - at least if I make sure to open the quest log once before talking to the NPC. For some reason the error only happens if the quest log was never opened since the last UI reload.
In reply to mcremor:
Yes, I had to disable the addon too, it breaks the game and is completely unusable. Hope the author can get it fixed, I despise the new-style questlog!
not sure if this error is the same:
9x FrameXML\QuestInfo.lua:389: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: QuestInfoSealFrame:SetPoint.
[C]: in function `SetPoint'
FrameXML\QuestInfo.lua:389: in function `?'
FrameXML\QuestInfo.lua:118: in function <FrameXML\QuestInfo.lua:51>
[C]: in function `QuestInfo_Display'
...rfaceClassic Quest Log\Classic Quest Log-1.4.2.lua:371: in function `UpdateQuestDetail'
...rfaceClassic Quest Log\Classic Quest Log-1.4.2.lua:356: in function `UpdateLog'
[string "*:OnUpdate"]:1: in function <[string "*:OnUpdate"]:1>
Locals:
(*temporary) = QuestInfoSealFrame {
0 = <userdata>
Text = <unnamed> {
}
Texture = <unnamed> {
}
}
(*temporary) = "CENTER"
(*temporary) = ClassicQuestLogDetailScrollChildFrame {
0 = <userdata>
}
No sooner did I post my last response than an error cropped up. I was accepting "The Legend of Mechagon", in case that helps:
Message: Interface\FrameXML\QuestInfo.lua:389: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: QuestInfoSealFrame:SetPoint.
Time: Thu Jul 4 18:40:14 2019
Count: 1
Stack: Interface\FrameXML\QuestInfo.lua:389: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: QuestInfoSealFrame:SetPoint.
[C]: in function `SetPoint'
Interface\FrameXML\QuestInfo.lua:389: in function `?'
Interface\FrameXML\QuestInfo.lua:118: in function <Interface\FrameXML\QuestInfo.lua:51>
[C]: in function `QuestInfo_Display'
Interface\FrameXML\QuestFrame.lua:493: in function <Interface\FrameXML\QuestFrame.lua:480>
[C]: in function `Show'
Interface\FrameXML\QuestFrame.lua:60: in function <Interface\FrameXML\QuestFrame.lua:20>
Locals: (*temporary) = QuestInfoSealFrame {
0 = <userdata>
Text = <unnamed> {
}
Texture = <unnamed> {
}
}
(*temporary) = "CENTER"
(*temporary) = QuestDetailScrollChildFrame {
0 = <userdata>
}
A note about the update just posted: There are possibly use cases that will possibly fail. I'm in the middle of reworking this addon for a more permanent fix.
In reply to gello3:
yeah i can confirm i get these with random quests (pick up or delivering)
145x FrameXML\QuestInfo.lua:389: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: QuestInfoSealFrame:SetPoint.
[C]: in function `SetPoint'
FrameXML\QuestInfo.lua:389: in function `?'
FrameXML\QuestInfo.lua:118: in function `QuestInfo_Display'
FrameXML\QuestFrame.lua:493: in function <FrameXML\QuestFrame.lua:480>
[C]: in function `Show'
FrameXML\QuestFrame.lua:60: in function <FrameXML\QuestFrame.lua:20>
Locals:
(*temporary) = QuestInfoSealFrame {
0 = <userdata>
Text = <unnamed> {
}
Texture = <unnamed> {
}
}
(*temporary) = "CENTER"
(*temporary) = QuestDetailScrollChildFrame {
0 = <userdata>
}
not giving up is already a good mind set :D,
i'm sure you will find a way eventually ^^ even if you have to ask for some idea's / help (there is no shame in that!),
and if you have to make some small sacrifices to make it work as it is now then so be i i guess .... (example no opening the log in combat)
'Thumbs up'
In reply to reaper666735:
I have an attack plan that I think will work. I'll keep you guys posted.
One compromise that probably will remain (for now) is the loss of the ability to have it behave like a "panel". So it will always be in undocked mode.
I think being able to summon it in combat is super important.