I'm creating this because the comment system on the Curse project page is horrendous - the comment nesting makes absolutely no sense whatsoever so it's extremely difficult to keep track of who said what in response to whom. This will be the official place to post feedback for the foreseeable future.
I am loving all of the changes, and your snarky change logs. I noticed that none of the Dalaran Underbelly rares alert now. I can add them manually, obviously, but is this intended?
They actually aren't rares, but I do have plans for them.
My intent is to diverge from being a Rare Tracker™ to more of a general-purpose NPC Tracker. The problem was, the old _NPCScan was a total mess and completely not engineered for what I wanted to do so I had to throw it away and start from scratch.
Cache hasn't been a concern since the launch of Warlords of Draenor; Blizzard completely broke the concept at that point.
There are two things to be aware of for re-detection, however: the Detection preferences tab has an Ignore section, with the settings "Completed Achievement Criteria" and "Completed Quest Objectives" - if either of these are true for any of the NPCs you'd like to have detect multiple times, they will not be detected so should the check box should be un-ticked.
You can tell if this is the case by finding the NPC in its location from the Zone tab: If the NPC name is red, it hasn't had its criteria met. If the name is green, it's been completed. Yellow means the NPC isn't being considered for any criteria.
Hey Torhal! First off I've been using NPC scan since..... I don't even know anymore, WOTLK maybe? It's been a while :P anyways thank you for all the work you have done with it!
One thing I'm finding a bit odd, we can't close a button in combat anymore, we used to be able to click the X on the popup of the old version. This is a bit of an issue as I have run into some areas that have a clump of 3 or more vignettes and got in combat, wasn't an issue at that time but I could see it being a problem in the wrong situation. Is this intended? I assume there is either a coding or taint limitation and that's why it was made that way.
In combat, the raid marker icon for the targeting button acts as a close button. Targeting buttons which don't have a raid marker icon - those spawned from a map vignette that haven't been updated with unit data - show a light blue normal close button when combat begins.
This is actually a limitation imposed by Blizzard, else I'd have right-click to dismiss work per usual.
I have a feature request. The Sha of Anger has 5 spawn points spaced rather far apart, and given how fast it dies to 110s you need to move FAST to get a kill. When it spawns, it yells one of the following 5 lines:
Give in to your anger
Your rage gives you strength!
Your rage sustains me!
You will not bury me again!
My wrath flows freely!
Would be really useful for NPCscan to trigger an alert when this happens.
Thank you for such a wonderful addon. I have used it for a very long time. I do have a bit of a problem at the moment, however, and am not sure what to do. I have the options set to 'not flash the red on my screen' and I have changed the choice of sound to the DF Roar Tauren. It is giving the roar, but also the default drums, and despite having the current update, and turning off the red flash, it still flashes red. I am not sure what to do to resolve this. Please help.
I actually downloaded the current version you mention before I posted here. I also logged back into the game and checked the settings, and made sure that the Screen Flash was 'unchecked', and the sound that shows as having been selected in DF Roar Tauren. Currently, every time I get near a Rare, dead or alive, the pops the small icon on the screen near my Mini-map, and the screen flashes, and both the default drums, and the DF Roar Tauren all go off at the same time. I don't know what else to do. I really like this addon, and prefer it to anything else.
I'm not seeing this behavior at all. To be sure this wasn't due to a difference in my SavedVariables, I completely exited the game, deleted Interface\WTF\Account/MyAccountName/SavedVariables/NPCScan.lua and then re-entered the game.
I turned off Screen Flash, removed both default sounds, and set a different sound. Then I found an NPC, targeted it, turned away from it so its nameplate wasn't in view, and from the NPCs->Custom panel typed the word "target" into the ID box. I then reloaded my UI to see if the War Drums sound returned; it did not. I turned back around so the custom NPC nameplate would trigger NPCScan, and there was no screen flash, and only the custom sound I'd set played.
My only two suggestions are:
Make sure _NPCScan isn't installed; just NPCScan - the former is the old AddOn.
The raid marker is the close button for the new targeting buttons. In the absence of a raid marker, as will happen when a targeting button is spawned via a map vignette, there is an actual close button.
Hi, firstly thanks for the addon, it's helped me out with killing things on numerous occasions. I have a question, however: how do I disable the "toast" notification in the bottom right corner? Really no need for two popups. Also, when I mouseover the other popup, it presents two options: left click or right click (one to target, one to dismiss) but neither of these seem to do anything?
Question... If I install the 'NPCScan', in game should it show up as '_NPCScan'? I have delete _NPCScan, _NPCSCAN Overlay, and _NPCScan Overlay Broker... When I pull up to see NPCScan in game, it insists on showing up as _NPCScan... Should this happen?
Note: It is no longer playing two sounds, just the War Drums. I had previously changed that to something that was just a little less 'loud'???... However, I did notice that I can't select any other sounds. Should their even be any others to obtain? Also, the box for showing the Red Flashing Screen is unchecked, and still flashes. I find this a bit hard on the eye.
Ok...Update: I found out that despite my efforts to delete/uninstall _NPCScan and associates, they were not being deleted. I manually deleted them and triple checked to make sure that it was not there. I have set the Flash to off, and the sounds are working fine... However, when I click on the tab that is marked NPCs, I get the following error:
Message: Interface\AddOns\NPCScan\Preferences\NPCs.lua:117: attempt to index field 'detection' (a nil value) Time: Thu Sep 15 11:59:33 2016 Count: 1 Stack: ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:249: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:197> ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1232: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1055> ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1588: in function `FeedGroup' ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1513: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1493> (tail call): ? [C]: ? [string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5> (tail call): ? ...face\AddOns\Altoholic\libs\AceGUI-3.0\AceGUI-3.0.lua:314: in function `Fire' ...ibs\AceGUI-3.0\widgets\AceGUIContainer-TreeGroup.lua:523: in function `Select' ...ibs\AceGUI-3.0\widgets\AceGUIContainer-TreeGroup.lua:531: in function `SelectByValue' ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1684: in function `FeedGroup' ... ...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:156: in function `SelectTab' ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1624: in function `FeedGroup' ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1513: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1493> (tail call): ? [C]: ? [string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5> (tail call): ? ...face\AddOns\Altoholic\libs\AceGUI-3.0\AceGUI-3.0.lua:314: in function `Fire' ...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:156: in function `SelectTab' ...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:67: in function <...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:64>
Locals: <none>
I am not able to go to that tab at all because of the LUA Error. Same with Detection and Targeting. And if I come across a Rare, it is still flashing red. I have set a different sound, but it still plays both that sound, and the War Drums. For now I will just leave it to the default sound, but am at a loss as to what to do for the Flashing Screen. Even after removing the alternate sound, it still wants to play both sounds at the same time. HELP! :( This is my favorite addon... Nobody else has anything even half as good.
I am using version 7.0.3.16 currently.
My apologies. You are going to get so tired of my adding on to this post. I once more uninstalled, manually, the NPCScan...and even triple checked that it was indeed gone. I waiting about a good hour or so, and logged back into the game. I unchecked the 'Flash Screen' and changed the sound to what I wanted. And I was even able to click on all of the tabs visible. This time I did not get any error, and 'knock-on-wood' (knocks on head) LOL... everything appears to be working and intended. Hopefully whatever the bug was is worked out. At least for now it all seems fine. THANK YOU, THANK YOU, THANK YOU, THANK YOU, THANK YOU, EVER so very much for your patience and for the wonderful addon.
Hi, firstly thanks for the addon, it's helped me out with killing things on numerous occasions. I have a question, however: how do I disable the "toast" notification in the bottom right corner? Really no need for two popups. Also, when I mouseover the other popup, it presents two options: left click or right click (one to target, one to dismiss) but neither of these seem to do anything?
Which version are you using?
The only time there should be a toast in the bottom right corner is if an NPC was detected while you were in combat, unless you also have _NPCScan installed. If that's the case, you should delete that - _NPCScan is the old version, whereas NPCScan is a completely new AddOn.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
AdminI'm creating this because the comment system on the Curse project page is horrendous - the comment nesting makes absolutely no sense whatsoever so it's extremely difficult to keep track of who said what in response to whom. This will be the official place to post feedback for the foreseeable future.
Bug Reports and Suggestions:
Issue Tracker
I am loving all of the changes, and your snarky change logs. I noticed that none of the Dalaran Underbelly rares alert now. I can add them manually, obviously, but is this intended?
-
View User Profile
-
View Posts
-
Send Message
AdminThey actually aren't rares, but I do have plans for them.
My intent is to diverge from being a Rare Tracker™ to more of a general-purpose NPC Tracker. The problem was, the old _NPCScan was a total mess and completely not engineered for what I wanted to do so I had to throw it away and start from scratch.
Sounds good to me. I went ahead and added them as custom, but just wanted to confirm. Very excited to see where you take this addon.
Will the new NPCscan still trigger if a mob spawns a second time (for like vignette mobs in MoP) or will i have to clear my cache each time?
-
View User Profile
-
View Posts
-
Send Message
AdminCache hasn't been a concern since the launch of Warlords of Draenor; Blizzard completely broke the concept at that point.
There are two things to be aware of for re-detection, however: the Detection preferences tab has an Ignore section, with the settings "Completed Achievement Criteria" and "Completed Quest Objectives" - if either of these are true for any of the NPCs you'd like to have detect multiple times, they will not be detected so should the check box should be un-ticked.
You can tell if this is the case by finding the NPC in its location from the Zone tab: If the NPC name is red, it hasn't had its criteria met. If the name is green, it's been completed. Yellow means the NPC isn't being considered for any criteria.
Hey Torhal! First off I've been using NPC scan since..... I don't even know anymore, WOTLK maybe? It's been a while :P anyways thank you for all the work you have done with it!
One thing I'm finding a bit odd, we can't close a button in combat anymore, we used to be able to click the X on the popup of the old version. This is a bit of an issue as I have run into some areas that have a clump of 3 or more vignettes and got in combat, wasn't an issue at that time but I could see it being a problem in the wrong situation. Is this intended? I assume there is either a coding or taint limitation and that's why it was made that way.
-
View User Profile
-
View Posts
-
Send Message
AdminIn combat, the raid marker icon for the targeting button acts as a close button. Targeting buttons which don't have a raid marker icon - those spawned from a map vignette that haven't been updated with unit data - show a light blue normal close button when combat begins.
This is actually a limitation imposed by Blizzard, else I'd have right-click to dismiss work per usual.
I have a feature request. The Sha of Anger has 5 spawn points spaced rather far apart, and given how fast it dies to 110s you need to move FAST to get a kill. When it spawns, it yells one of the following 5 lines:
Would be really useful for NPCscan to trigger an alert when this happens.
-
View User Profile
-
View Posts
-
Send Message
AdminIf you don't want that suggestion to get lost, please post it on the Issue Tracker.
You said this was the place to post feedback and ideas, but sure, will do.
Thank you for such a wonderful addon. I have used it for a very long time. I do have a bit of a problem at the moment, however, and am not sure what to do. I have the options set to 'not flash the red on my screen' and I have changed the choice of sound to the DF Roar Tauren. It is giving the roar, but also the default drums, and despite having the current update, and turning off the red flash, it still flashes red. I am not sure what to do to resolve this. Please help.
-
View User Profile
-
View Posts
-
Send Message
AdminAre you using version 7.0.3.16? The default War Drums returning after being removed was fixed in 7.0.3.12.
If you go to Alerts->Screen Flash there is an Enable checkbox. Un-checking that will disable the screen flashing.
I actually downloaded the current version you mention before I posted here. I also logged back into the game and checked the settings, and made sure that the Screen Flash was 'unchecked', and the sound that shows as having been selected in DF Roar Tauren. Currently, every time I get near a Rare, dead or alive, the pops the small icon on the screen near my Mini-map, and the screen flashes, and both the default drums, and the DF Roar Tauren all go off at the same time. I don't know what else to do. I really like this addon, and prefer it to anything else.
-
View User Profile
-
View Posts
-
Send Message
AdminI'm not seeing this behavior at all. To be sure this wasn't due to a difference in my SavedVariables, I completely exited the game, deleted Interface\WTF\Account/MyAccountName/SavedVariables/NPCScan.lua and then re-entered the game.
I turned off Screen Flash, removed both default sounds, and set a different sound. Then I found an NPC, targeted it, turned away from it so its nameplate wasn't in view, and from the NPCs->Custom panel typed the word "target" into the ID box. I then reloaded my UI to see if the War Drums sound returned; it did not. I turned back around so the custom NPC nameplate would trigger NPCScan, and there was no screen flash, and only the custom sound I'd set played.
My only two suggestions are:
I would like a way to close these pop ups in combat, like the old version, I could click on the X, and gone. I will try the raid marker ....
To the poster above, the red screen can also be generated by Z-Perl / X-perl .....
-
View User Profile
-
View Posts
-
Send Message
AdminThe raid marker is the close button for the new targeting buttons. In the absence of a raid marker, as will happen when a targeting button is spawned via a map vignette, there is an actual close button.
Hi, firstly thanks for the addon, it's helped me out with killing things on numerous occasions. I have a question, however: how do I disable the "toast" notification in the bottom right corner? Really no need for two popups. Also, when I mouseover the other popup, it presents two options: left click or right click (one to target, one to dismiss) but neither of these seem to do anything?
Question... If I install the 'NPCScan', in game should it show up as '_NPCScan'? I have delete _NPCScan, _NPCSCAN Overlay, and _NPCScan Overlay Broker... When I pull up to see NPCScan in game, it insists on showing up as _NPCScan... Should this happen?
Note: It is no longer playing two sounds, just the War Drums. I had previously changed that to something that was just a little less 'loud'???... However, I did notice that I can't select any other sounds. Should their even be any others to obtain? Also, the box for showing the Red Flashing Screen is unchecked, and still flashes. I find this a bit hard on the eye.
Ok...Update: I found out that despite my efforts to delete/uninstall _NPCScan and associates, they were not being deleted. I manually deleted them and triple checked to make sure that it was not there. I have set the Flash to off, and the sounds are working fine... However, when I click on the tab that is marked NPCs, I get the following error:
Message: Interface\AddOns\NPCScan\Preferences\NPCs.lua:117: attempt to index field 'detection' (a nil value)
Time: Thu Sep 15 11:59:33 2016
Count: 1
Stack: ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:249: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:197>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1232: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1055>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1588: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1513: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1493>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...face\AddOns\Altoholic\libs\AceGUI-3.0\AceGUI-3.0.lua:314: in function `Fire'
...ibs\AceGUI-3.0\widgets\AceGUIContainer-TreeGroup.lua:523: in function `Select'
...ibs\AceGUI-3.0\widgets\AceGUIContainer-TreeGroup.lua:531: in function `SelectByValue'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1684: in function `FeedGroup'
...
...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:156: in function `SelectTab'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1624: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1513: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1493>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...face\AddOns\Altoholic\libs\AceGUI-3.0\AceGUI-3.0.lua:314: in function `Fire'
...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:156: in function `SelectTab'
...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:67: in function <...libs\AceGUI-3.0\widgets\AceGUIContainer-TabGroup.lua:64>
Locals: <none>
I am not able to go to that tab at all because of the LUA Error. Same with Detection and Targeting. And if I come across a Rare, it is still flashing red. I have set a different sound, but it still plays both that sound, and the War Drums. For now I will just leave it to the default sound, but am at a loss as to what to do for the Flashing Screen. Even after removing the alternate sound, it still wants to play both sounds at the same time. HELP! :( This is my favorite addon... Nobody else has anything even half as good.
I am using version 7.0.3.16 currently.
My apologies. You are going to get so tired of my adding on to this post. I once more uninstalled, manually, the NPCScan...and even triple checked that it was indeed gone. I waiting about a good hour or so, and logged back into the game. I unchecked the 'Flash Screen' and changed the sound to what I wanted. And I was even able to click on all of the tabs visible. This time I did not get any error, and 'knock-on-wood' (knocks on head) LOL... everything appears to be working and intended. Hopefully whatever the bug was is worked out. At least for now it all seems fine. THANK YOU, THANK YOU, THANK YOU, THANK YOU, THANK YOU, EVER so very much for your patience and for the wonderful addon.
-
View User Profile
-
View Posts
-
Send Message
Admin