nQuestLog - WoW AddOns

Questing minion
---

August 20, 2009: I have started the tear-down/rebuild of this addon and will keep this description updated as I go. My path will be:
1) DONE - Thanks Fyrye. Update the libraries so we can get it working without yelling at you, albeit with a bit of tweaking
2) Update the code to work with the new questlog api
3) Recode and reduction of external library dependancy

You must login to post a comment. Don't have an account? Register to get one!

81 comments
1
2
3
4
5
6
7
8
9
Next →

- #83
Radoznali Sat, 19 Dec 2009 23:27:05
anyone knows how to solve problem with this addon-it removes objective frame so i have trouble seeing /tracking achivements?
- #82
scrumbus Mon, 14 Dec 2009 23:56:46
Likewise, thanks for the tip on the fix.
- #81
ff123 Sun, 13 Dec 2009 05:47:27
thank you very much for the fix, myrathi2!!
- #80
myrathi2 Sun, 13 Dec 2009 00:38:17
Ok. Quick-fix that seems to work across a couple of similar quests (on different alts) is a modification to only Quixote, treating a 'log' leaderboard entry just like an 'event' one: it has a 'textual requirement' and is either completed or not.

This is, as far as I can tell, identical to how Blizzard's own code seems to treat it, as they simply append " (Complete)" to the text in the default quest description panel if the finished variable equates to true.

The hack works fine for me, anyway, so I hope it fixes the issue for others, also.

Let me know if there are any problems (other than having multiple addons that embed a Quixote-1.0 lib :P)...

File: /nQuestLog/libs/Quixote-1.0/Quixote-1.0.lua
Line: ~329

Change:
elseif qtype == 'event' then
To:
elseif qtype == 'event' or qtype == 'log' then
- #79
myrathi2 Sat, 12 Dec 2009 23:47:57
Found the problem. It's a leaderboard type that's screwing things up (unsurprisingly), since Quixote isn't handling it correctly. Specifically, type="log".

The Terokkar quest "Seek Out Kirrik" is the example that's killing my nQL (on an alt).

Simple enough to hack a fix into nQL but a proper solution requires modifications to both (Quixote needs to handle the new type and nQL needs to display it properly).

Will post again if/when I figure out a decent way to deal with it. :P
- #78
Radoznali Sat, 12 Dec 2009 16:30:46
any news on updates ?or if someone is going to update it at all?
- #77
ff123 Fri, 11 Dec 2009 03:15:20
Hopefully this just needs a minor lua code update to comply with the new blizz tracking features, since only certain types of quests break it like Des mentioned. I really hope someone is able to fix this every other minion out there sucks and the default blizz tracker is garbage. I'll try to post an error code the next it breaks for me.
- #76
Des555 Thu, 10 Dec 2009 17:00:25
I have nquestlog working fine with patch 3.3 .. that is until you pick up a quest that's instantly complete, then lots of error messages, until you hand that quest in, then it's fine again .. any ideas if there's anything I can do about this ?

btw I did same as ff123 and emptied quest log then re-enabled nquestlog before using it

Last edited on 10 Dec 2009 by Des555
- #75
zaphon Wed, 09 Dec 2009 01:11:00
I just grabbed the latest Fyrye branch of nQuestLog and it blows up all over the place just like my own branch does. So not sure how/why yours is working, but I'm getting all kinds of errors (including I can't drop any quests while nQuestLog is loaded). :-) Logging back out to disable.
- #74
ff123 Wed, 09 Dec 2009 00:47:59
not sure of it works for everyone but i abandoned all my quests, restarted the game and re-enabled nquestlog and now it works perfectly.

Last edited on 09 Dec 2009 by ff123