Authors CurseForge

Every time i accept a quest i get this:

[21:50:33] Quest accepted: Windroc Mastery
[21:50:33] Windroc Mastery
0
[21:50:37] Quest accepted: Clefthoof Mastery
[21:50:37] Clefthoof Mastery
0
[21:50:39] Quest accepted: Talbuk Mastery
[21:50:39] Talbuk Mastery
0



Is this some kind of debug info or something? This started happening since the latest update.

yeah I forgot some debug in the latest release I'll update a correction :)

On login with r101:


[2009/04/10 12:43:56-2101-x1]: AceLocale-3.0: tomQuest2-Core: Missing entry for 'Use special quest item':
tomQuest2-101\core.lua:1239: in main chunk

---

Quote from X-buZZ

Hi there,

i just discovered this addon and i like it very much.
However, i am missing some features from nQuestlog:

- options for font outlines (when hiding background and border texts are much better visible with outlines)

- custom colors of all elements (When turning off the coloring for specific elements the just get white. I want for instance the quest headers or quest texts to have custom colors rather then level colored or just white)

- custom completition coloring (Because i like to have quests goals with 0% to be colored in gray :)

Keep up the great work!

Kind regards
X-buZZ

I'll see what I can do :)

latest release include font ouline and default color

I just need to do custom color for quest objective

Sorry to say, but there are once again lots of errors on login with r103. Below are a few (of 13):

[2009/04/11 00:05:35-2107-x1]: tomQuest2-103\achievementTracker.lua:423: attempt to index upvalue 'prdb' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (ButtonFacade):518: in function <...dOns\ButtonFacade\Libs\AceAddon-3.0\AceAddon-3.0.lua:511>
(tail call): ?:
(tail call): ?:
tomQuest2-103\core.lua:257: in function `?'
CallbackHandler-1.0-3:146: in function <...ade\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[3]":4: in function <[string "safecall Dispatcher[3]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[3]":13: in function `?'
CallbackHandler-1.0-3:91: in function `Fire'
AceDB-3.0-13 (DockingStation):575: in function `ResetDB'
tomQuest2-103\core.lua:228: in function <Interface\AddOns\tomQuest2\core.lua:219>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (ButtonFacade):491: in function `InitializeAddon'
AceAddon-3.0-5 (ButtonFacade):604: in function <...dOns\ButtonFacade\Libs\AceAddon-3.0\AceAddon-3.0.lua:597>

---

[2009/04/11 00:05:35-2107-x1]: tomQuest2-103\achievementTracker.lua:440: attempt to index field 'db' (a nil value)
tomQuest2-103\core.lua:262: in function `?'
CallbackHandler-1.0-3:146: in function <...ade\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[3]":4: in function <[string "safecall Dispatcher[3]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[3]":13: in function `?'
CallbackHandler-1.0-3:91: in function `Fire'
AceDB-3.0-13 (DockingStation):575: in function `ResetDB'
tomQuest2-103\core.lua:228: in function <Interface\AddOns\tomQuest2\core.lua:219>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (ButtonFacade):491: in function `InitializeAddon'
AceAddon-3.0-5 (ButtonFacade):604: in function <...dOns\ButtonFacade\Libs\AceAddon-3.0\AceAddon-3.0.lua:597>

---

[2009/04/11 00:05:35-2107-x1]: tomQuest2-103\achievementTracker.lua:440: attempt to index field 'db' (a nil value)
tomQuest2-103\core.lua:262: in function `Refresh'
tomQuest2-103\core.lua:229: in function <Interface\AddOns\tomQuest2\core.lua:219>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (ButtonFacade):491: in function `InitializeAddon'
AceAddon-3.0-5 (ButtonFacade):604: in function <...dOns\ButtonFacade\Libs\AceAddon-3.0\AceAddon-3.0.lua:597>

---

[2009/04/11 00:05:35-2107-x1]: tomQuest2-103\config.lua:242: attempt to index field 'optionsFrames' (a nil value)
tomQuest2-103\questsTracker.lua:873: in function <Interface\AddOns\tomQuest2\questsTracker.lua:868>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (ButtonFacade):491: in function `InitializeAddon'
AceAddon-3.0-5 (ButtonFacade):604: in function <...dOns\ButtonFacade\Libs\AceAddon-3.0\AceAddon-3.0.lua:597>

---




Also, blizz options looks really weird: http://bildr.no/view/386832

Oh and savedvariables got flushed again (dunno if that was intended)

argh don't know what's happening, I need to check but I'll be out for the next three days

and the options are weird, I don't get it like that on my client.

also is it the same thing after a reload?

Deleted my savedvariables manually and 103beta seems to be working fine now without errors.

i just came back, I'll check tonight when going back from work why I get those errors.

Also skylinee do you still get the strange option panel?

Quote from gagou

i just came back, I'll check tonight when going back from work why I get those errors.

Also skylinee do you still get the strange option panel?

No, everything is working perfectly with the latest version. I guess the manual deletion of Savedvariables did the thing.

I just uploaded r105 which should work much better and should have proper profiles support, here is the changelog:

update toc version
fix syncParty, tagQuestLog, tagQuestGivers module not activated
fix profiles and db versioning
fix mob tooltip display
add font outline to achievement tracker
fix key binding
add custom objectives coloring function
add option to hide default blizzard quest and achievement tracker

Wanted to give this a shot, since nQuestLog appears to be dead, but can't get it to load.

First, it complained about finding the AceUI-3.0 and AceOptionsDB-3.0 libraries. I added those, but then it started complaining that it was unable to get the "isTrackable" string.

Not only that, once I disable it, it completely screws up the default Blizzard quest tracking, as it says that I have too many trackable quests.

I have to delete the WTF folder to correct it.

Quick question, in Blizzards new advanced quest tracker, if you need to use an item it shows up you can click on in the tracker. Does tomQuest2 also provide this feature, or are you just able to hotkey it?

Quote from jexxlc

Quick question, in Blizzards new advanced quest tracker, if you need to use an item it shows up you can click on in the tracker. Does tomQuest2 also provide this feature, or are you just able to hotkey it?

The only thing you can do right now is to alt right click on the quest to create / update a macro with quests objects that you can put on your action bar, each time you alt right click on a quest with an object the macro will be updated to use the correct object

Quote from mkong409

Wanted to give this a shot, since nQuestLog appears to be dead, but can't get it to load.

First, it complained about finding the AceUI-3.0 and AceOptionsDB-3.0 libraries. I added those, but then it started complaining that it was unable to get the "isTrackable" string.

Not only that, once I disable it, it completely screws up the default Blizzard quest tracking, as it says that I have too many trackable quests.

I have to delete the WTF folder to correct it.

Will check those library errors, were you using nolib or standard package?
do you have the full error with "isTrackable" ?

for the library I'll push an update tonight to include those two in the pkgmeta and toc file

Quote from gagou

Will check those library errors, were you using nolib or standard package?
do you have the full error with "isTrackable" ?

I was using standard.

I'll get you the error as soon as I can, servers were down as I write this.

(and were down when I sent the original message, or else I'd have it for you). ;)

Quote from mkong409

I was using standard.

I'll get you the error as soon as I can, servers were down as I write this.

(and were down when I sent the original message, or else I'd have it for you). ;)

Thank you. I'll look into it as soon as I can