Right-click your minion and you can check off what you want to see or not.
I've checked off everythign I can. What i'm asking is for some more of the SmartVisibility behaviour to help me save space even more. This feature rocks and does a good job, but if it could do a little more I could save half or more of my minion space.
I'm not able to get LightHeaded comments to display. I'm up to date on both LightHeaded and nQuestLog. Any ideas?
Not sure if this is related:
[2007/10/07 09:21:58-19-x1]: nQuestLog-1.0\modules\DetailsFrame\DetailsFrame.lua:76: attempt to index global 'escapeDetector' (a nil value)
[2007/10/07 09:28:01-19-x1]: nQuestLog-1.0\modules\Comments\Comments.lua:144: bad argument #1 to 'pairs' (table expected, got nil)
nQuestLog-1.0\modules\Comments\Comments.lua:144: in function `GetMobMapQuestIdByName'
nQuestLog-1.0\modules\Comments\Comments.lua:363: in function `runChildren'
Tablet-2.0-49630 (TabletLib):2355: in function `children'
Tablet-2.0-49630 (TabletLib):2399: in function `Open'
nQuestLog-1.0\modules\Comments\Comments.lua:504: in function `Update'
nQuestLog-1.0\modules\Comments\Comments.lua:126: in function <...rface\AddOns\nQuestLog\modules\Comments\Comments.lua:124>
(tail call): ?:
<in C code>: in function `UpdateQuestDetail'
nQuestLog-1.0\modules\DetailsFrame\DetailsFrame.lua:78: in function `ShowLog'
nQuestLog-1.0\events.lua:258: in function <Interface\AddOns\nQuestLog\events.lua:255>
<in C code>: in function `ShowLog'
nQuestLog-1.0\events.lua:291: in function `OnQuestLogClickQuest'
nQuestLog-1.0\events.lua:79: in function `OnQuestLogClick'
<string>:"*:OnMouseDown":5: in function <[string "*:OnMouseDown"]:1>
I'm not able to get LightHeaded comments to display. I'm up to date on both LightHeaded and nQuestLog. Any ideas?
Not sure if this is related:
[2007/10/07 09:21:58-19-x1]: nQuestLog-1.0\modules\DetailsFrame\DetailsFrame.lua:76: attempt to index global 'escapeDetector' (a nil value)
[2007/10/07 09:28:01-19-x1]: nQuestLog-1.0\modules\Comments\Comments.lua:144: bad argument #1 to 'pairs' (table expected, got nil)
nQuestLog-1.0\modules\Comments\Comments.lua:144: in function `GetMobMapQuestIdByName'
nQuestLog-1.0\modules\Comments\Comments.lua:363: in function `runChildren'
Tablet-2.0-49630 (TabletLib):2355: in function `children'
Tablet-2.0-49630 (TabletLib):2399: in function `Open'
nQuestLog-1.0\modules\Comments\Comments.lua:504: in function `Update'
nQuestLog-1.0\modules\Comments\Comments.lua:126: in function <...rface\AddOns\nQuestLog\modules\Comments\Comments.lua:124>
(tail call): ?:
<in C code>: in function `UpdateQuestDetail'
nQuestLog-1.0\modules\DetailsFrame\DetailsFrame.lua:78: in function `ShowLog'
nQuestLog-1.0\events.lua:258: in function <Interface\AddOns\nQuestLog\events.lua:255>
<in C code>: in function `ShowLog'
nQuestLog-1.0\events.lua:291: in function `OnQuestLogClickQuest'
nQuestLog-1.0\events.lua:79: in function `OnQuestLogClick'
<string>:"*:OnMouseDown":5: in function <[string "*:OnMouseDown"]:1>
This is the same problem that fyrye reported a few days ago. Although the code works just fine, I think the generic frame name "escapeDetector" is being used by another addon and breaking nQuestLog as a result. I'll be releasing a fix today with that frame renamed, as well as some other fixes and new features. Thanks.
This error appears whenever I mouse over a party pet frame. I use xperl unitframes and tinytip for tooltips, if that makes a difference.
Error: bad argument #2 to 'find' (string expected, got nil)
AddOn: nQuestLog
File: Tooltips.lua
Line: 121
Thanks for the report. I'm redoing the unit tooltip and adding a lot of error-checking to it to hopefully prevent errors like this from occurring. This fix should be implemented today.
I have been getting this error since patch 2.2 ( mod doesn't work at all, getting that error when i want to show the minion ):
Interface\AddOns\nQuestlog\modules\moduleLoading.lua:86: attempt to index field 'db' (a nil value)
Tried deleting the mod and WTF files but didn't help, some guidance would be appreciated.
Sorry, I can't troubleshoot this one, as I can't see how this error could possibly occur after looking at the code. This appears to only be on your end, so I would advise disabling all addons and just running a fresh, current install of nQuestLog to see if the error still occurs (it shouldn't). Then, reenable addons until you find the conflict (if there is still a conflict).
Okay, I just uploaded the fixes and new features. For those who use MobMap, you'll now have a very nice feature available to you automatically -- updating of mob tooltips with mob quest objectives based on the MobMap drop table for that mob! Other new features include font outline option, disabling mob tooltip processing while raiding, and preventing the minion from moving off screen. Alright, time to get some sleep!
I have been getting this error since patch 2.2 ( mod doesn't work at all, getting that error when i want to show the minion ):
Interface\AddOns\nQuestlog\modules\moduleLoading.lua:86: attempt to index field 'db' (a nil value)
Tried deleting the mod and WTF files but didn't help, some guidance would be appreciated.
This has something to do with the escapeDetector as well, I presume you use the MazzleUI mod and commented out the line where it calls for nQuestLog:GetModule("DetailsFrame"):ShowLog();
Uncomment those lines out, and download the updated nQuestLog to see if it works with out error.
Okay, I just uploaded the fixes and new features. For those who use MobMap, you'll now have a very nice feature available to you automatically -- updating of mob tooltips with mob quest objectives based on the MobMap drop table for that mob! Other new features include font outline option, disabling mob tooltip processing while raiding, and preventing the minion from moving off screen. Alright, time to get some sleep!
Very sweet! Thank you. Ill test drive it when I get home from work. Ill also look to see if any of my mods are using "escapeDetector" and let you know which one/s they are.
Well, it's renamed now anyway and declared locally instead of globally, so it should be impossible to get that error now. You might want to also search the contents of your .xml files, too, as it could be declared in one of those. It's a moot point now, though. :)
Another example of the tooltip showing funny stuff:
I did the quest "I Work... For the Horde!", where you have to gather Salvaged Metal x 8 and Salvaged Wood x 8. Which is junk that just lies on the ground near Thrallmar. Yet when I hover over a Bonechewer Scavenger (plenty of those in the area), the tooltip shows them as dropping both. :) Which they do not, and their name isn't even similar to the items I need.
Another example of the tooltip showing funny stuff:
I did the quest "I Work... For the Horde!", where you have to gather Salvaged Metal x 8 and Salvaged Wood x 8. Which is junk that just lies on the ground near Thrallmar. Yet when I hover over a Bonechewer Scavenger (plenty of those in the area), the tooltip shows them as dropping both. :) Which they do not, and their name isn't even similar to the items I need.
Hmm, are those items in the MobMap loot table for Bonechewer Scavengers? If so, I can't filter out bad data, and you can just disable using MobMap in the nQuestLog mob tooltip settings if you do not wish to use it. At this point, there should be no false positives, unless the data in MobMap is incorrect, which occasionally happens.
Hmm, are those items in the MobMap loot table for Bonechewer Scavengers? If so, I can't filter out bad data, and you can just disable using MobMap in the nQuestLog mob tooltip settings if you do not wish to use it. At this point, there should be no false positives, unless the data in MobMap is incorrect, which occasionally happens.
I checked Wowhead and found similar bad data for Bonechewer Evoker with a drop rate that rounds to 0%. To combat this, I'm going to add a threshold option, probably defaulted to 1-2% or so, that allows you to ignore matches below that threshold. I'll take a look at what MobMap has as the drop rate for that item, and hopefully this will further prevent any false positives. :)
Edit: Ok, this is added. I set the default to 1%, which should filter most false positives, but you can drop it to 0% to disable filtering or increase it to whatever % value you want to use as a threshold. I also added an option to enable/disable displaying the drop rate in the tooltip.
Is there any option to hide the orig quest notes that appear under the MiniMapCluster frame?
Im getting those showing in addition to the minion but see nowhere in NQuestlog to turn it off...
Thanks for any info!
This is the Blizzard quest tracking. You'll need to open your standard quest log, shift-click any tracked quests, and then go into the Blizzard options and disable automatic quest tracking. That should take care of it for you.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI've checked off everythign I can. What i'm asking is for some more of the SmartVisibility behaviour to help me save space even more. This feature rocks and does a good job, but if it could do a little more I could save half or more of my minion space.
Strike that, one was added recently... thank you!!!
Interface\AddOns\nQuestlog\modules\moduleLoading.lua:86: attempt to index field 'db' (a nil value)
Tried deleting the mod and WTF files but didn't help, some guidance would be appreciated.
Not sure if this is related:
Error: bad argument #2 to 'find' (string expected, got nil)
AddOn: nQuestLog
File: Tooltips.lua
Line: 121
This is the same problem that fyrye reported a few days ago. Although the code works just fine, I think the generic frame name "escapeDetector" is being used by another addon and breaking nQuestLog as a result. I'll be releasing a fix today with that frame renamed, as well as some other fixes and new features. Thanks.
Thanks for the report. I'm redoing the unit tooltip and adding a lot of error-checking to it to hopefully prevent errors like this from occurring. This fix should be implemented today.
Sorry, I can't troubleshoot this one, as I can't see how this error could possibly occur after looking at the code. This appears to only be on your end, so I would advise disabling all addons and just running a fresh, current install of nQuestLog to see if the error still occurs (it shouldn't). Then, reenable addons until you find the conflict (if there is still a conflict).
This has something to do with the escapeDetector as well, I presume you use the MazzleUI mod and commented out the line where it calls for nQuestLog:GetModule("DetailsFrame"):ShowLog();
Uncomment those lines out, and download the updated nQuestLog to see if it works with out error.
Very sweet! Thank you. Ill test drive it when I get home from work. Ill also look to see if any of my mods are using "escapeDetector" and let you know which one/s they are.
I did the registry mod to search lua files here
To WoW I go.
Well, it's renamed now anyway and declared locally instead of globally, so it should be impossible to get that error now. You might want to also search the contents of your .xml files, too, as it could be declared in one of those. It's a moot point now, though. :)
I did the quest "I Work... For the Horde!", where you have to gather Salvaged Metal x 8 and Salvaged Wood x 8. Which is junk that just lies on the ground near Thrallmar. Yet when I hover over a Bonechewer Scavenger (plenty of those in the area), the tooltip shows them as dropping both. :) Which they do not, and their name isn't even similar to the items I need.
Hmm, are those items in the MobMap loot table for Bonechewer Scavengers? If so, I can't filter out bad data, and you can just disable using MobMap in the nQuestLog mob tooltip settings if you do not wish to use it. At this point, there should be no false positives, unless the data in MobMap is incorrect, which occasionally happens.
I checked Wowhead and found similar bad data for Bonechewer Evoker with a drop rate that rounds to 0%. To combat this, I'm going to add a threshold option, probably defaulted to 1-2% or so, that allows you to ignore matches below that threshold. I'll take a look at what MobMap has as the drop rate for that item, and hopefully this will further prevent any false positives. :)
Edit: Ok, this is added. I set the default to 1%, which should filter most false positives, but you can drop it to 0% to disable filtering or increase it to whatever % value you want to use as a threshold. I also added an option to enable/disable displaying the drop rate in the tooltip.
Im getting those showing in addition to the minion but see nowhere in NQuestlog to turn it off...
Thanks for any info!
This is the Blizzard quest tracking. You'll need to open your standard quest log, shift-click any tracked quests, and then go into the Blizzard options and disable automatic quest tracking. That should take care of it for you.