Get an Epic Experience with Premium


Achievements Login to Add Favorites
  • World of Warcraft
  • 546,719 Monthly Downloads
  • Supports: 5.4.8
  • 20,680,382 Total Downloads
  • Updated 08/25/2014
  • Created 06/06/2009
  • 9,674 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File:
Support development! **

About _NPCScan

_NPCScan & Warlords

Due to changes in how the game caches mobs in WoD, it is looking like _NPCScan will no longer be able to auto detect non-Vignette mobs. Due to this the only way to find pre-MoP rares via _NPCScan will be via mouse over or the new dynamic target macro keybind being added. The new keybind will trigger a /targetexact …” macro that updates with tracked mobs based on the zone you are currently in. Vignette mobs will still automatically trigger an alert when the mob gets in range, and should work more reliably due to updates to the Vignette API.

_NPCScan tracks seldom-seen rare mobs by proximity alone, making the old “/targetexact …” macros obsolete. It has the same range as those targeting macros, but you won't have to mash any buttons. Just go about your business and let _NPCScan alert you when it finds something.

V5.x Changes
  • Due to changes in how the addon stores data, some settings might get reset when updating.
  • The default alert is suppressed while on flight paths by default. If a mob is found, the whisper sound effect will play and the mob & location will be placed in the chat log. You can turn this off from the settings.
  • _NPCScan now includes all rare mobs in the game.
  • The "One of Many", "Timeless Champion" & "Champions of Lei Shen" Achievements have been added.
  • Rare Mobs and Tameable Mobs have their own tabs now.
  • Custom mobs have been added for the Ghostly Pandaren Fisherman & Craftsman.
  • Individual mobs can be removed from their tabs to stop tracking them.

If you have a question check the FAQ, or a problem create a ticket

If you have a question/comment about _NPCScan.Overlay please post it in it's comment section.



NPCScan now tracks "vignettes". These are the little skulls appear on the minimap, that denote rare mobs. This is a beta feature and is disabled by default. Enabling this feature will alert you to a rare that's within minimap range, without any worries about having to clear your cache. When you get an alert you will be shown a target button similar to the standard mob alert, letting you know that a vignette mob was detected. Clicking on the target button will try and target the mob. Once a mob is targeted, the target button will update to reflect the mob found.

Known Issues: Currently there is no way to detect what mob the vignette represents. Because of this there is no way to filter out and ignore individual mobs. The vignette tracking will ignore achievement mobs groups that have their tracking turned of via unchecking their tab. Also the targeting button might have some issues if there are more than one vignette mobs in target range and may not work 100% of the time.

The Cache

This addon doesn't use nameplates or mouseover units to find rares. Instead, it checks your creature cache for the moment a rare mob is found. There is one catch to this technique however: Once a mob is “found”, _NPCScan won't be able to find it again until your cache is clearedf you find a rare mob's corpse—Dirkee for example—you would have to clear your cache before _NPCScan would find Dirkee again. Thankfully, clearing your cache is a safe and simple matter.

Clearing Your Cache

To clear your cache, follow these straightforward steps:

  1. Exit World of Warcraft
  2. Delete the “Cache” sub-directory inside your World of Warcraft folder.  For example on a standard Windows XP installation, you would delete the folder “C:\Program Files\World of Warcraft\Cache”.
  • Advanced users can delete “C:\Program Files\World of Warcraft\Cache\WDB\enUS\creaturecache.wdb” specifically to improve log-in times, where enUS is your language code.

Note: Windows Vista and Windows 7 users see this info if your cache isn't in the location above.

That's it. Log in after you've done that and you'd be able to find Dirkee a second time. It's completely safe because WoW will recreate your Cache folder after you log in again.

Cache Warning

If a rare mob is already cached when you log in, _NPCScan will print a warning message with the names of those mobs. If you see this message but still want to find the listed NPCs again, it's time to clear your cache by following the above procedure; Otherwise, you can quit searching for those mobs using the Search options window detailed below. You can suppress this log-in message using the main options pane, as well.

“Found” Alert

When a rare mob is found, _NPCScan alerts you by playing a loud and distinctive sound, making your screen pulse red, and displaying an animated Targeting Button. To get a feel for what this alert looks and sounds like, try the “Test Found Alert” button in the addon's main Interface Options panel. (See the Options section below.)

Targeting Button

When clicked, the targeting button tries to target the most-recently-found mob.  You can also bind a key to hit this button. If the default button position isn't to your liking, you can move it while holding your CTRL key.

Note: The button cannot be shown during combat. In the unlikely case that you do find a rare while fighting, the button will appear after you leave combat. You will still hear the alert however, and the name of the mob will appear in your chat log.


_NPCScan's main options window can be accessed from the Interface Options menu. This panel includes a “Test Found Alert” button, various ways to customize the alert sound, and an option to suppress cache warning messages on log-in. New sounds can be added to the alert sound dropdown menu by installing SharedMedia-type addons.

Search List

The list of mobs that _NPCScan searches for can be modified easily through the Interface Options panel, however it comes pre-configured with most rare Outlands and Northrend mobs.; To access the mob list, type “/npcscan”. Grayed out NPCs in a list aren't being searched for, either because they're cached or not needed for their achievement.

The first tab available lists Custom NPCs that you can enter or remove manually. NPCs that are already cached show a red “X” in the first column. You can add or remove Custom NPCs with the [+] and [-] buttons at the bottom right.

All other tabs control achievements like Bloody Rareand Frostbitten. These tabs show an additional column on the right with green check marks for completed achievement mobs. You may enable or disable tracking each achievement with its tab's checkbox.

To remove non custom mobs from a tab, click on the mob that you want to remove and then click on the "Remove" button. This will remove the selected mob from the current tab and add it to the Ignore List Tab. If you ever want to restore a Ignored Mob, select it from the "Ignore List" tab, click the "Remove" button and it should be added back to its original tab.

The “Search for completed Achievement NPCs” checkbox at the top left of the pane allows you to keep looking for mobs you no longer need for achievements.

Finding NPC IDs

A mob's NPC ID is its unique identification number, and it can be found on sites like WowHead or WowDB For example, search for the mob “Dirkee” on WowHead and go to the mob's page.  That page's URL will look like

32500 is Dirkee's NPC ID.


The only problem mobs for _NPCScan are tamable beasts & Battle Pets. Whenever you run across the tamed version, _NPCScan gets tricked into thinking that mob is nearby. In order to prevent those false positives, _NPCScan only shows alerts for tamable mobs in their original zones That is, if you spot Loque'nahak in Dalaran instead of Sholazar Basin where it usually patrols, _NPCScan would ignore it. When one of these tamable mob false-alarms happens, you'll see a message in your chat window explaining why it got ignored.

Since this makes tamable mobs are so difficult to track, I suggest you fly to the tamable mob's zone first, clear your cache, and then search for it.; Any time you pass through a populated area like Dalaran, you risk filling your cache with popular rare pets.

For Battle Pets there is no way for it to determine if a mob is a spawn or someone's pet. Many Battle Pet addons and just opening the Pet Journal will often cause Battle Pets to become cached.

James D. Callahan III <>
2014-08-25 19:12:48 -0500


James D. Callahan III:
    - Moved CacheWarnings option to global from per-character.
    - Cleanups
    - Removed commented-out code.


First Previous Page 112 of 150 Next Last
  • #1043 fact, even something so simple as to show the area I have already travelled for any specified duration of time would be significantly helpful.
  • #1044
    The range ring from _NPCScan.Overlay is as close as a mod can come to guessing the range of mobs that're loaded by your game. I recommend also downloading Carbonite and configuring its red trail effect to stay visible for a few minutes. I think Carbonite also lets you adjust the width of the trail, although I can't remember where either of these settings are. If you can get the trail to stay shown for about 5 minutes and match its width to _NPCScan.Overlay's range ring, that should come close to what you're asking for.
  • #1038
    I really love this addon. I do have a suggestion though, can you add a setting to turn off caching?
  • #1041
    The game caches mobs whether _NPCScan is on or not, so there's no way to disable it.
  • #1035
    My problem is the following.
    I updated this very useful addon with curseclient after 4.0 has came to live servers.

    Now, I found a rare mob (only because the mob were nicer than the others and I flew near him and saw it's Old Crystalbark)and the addon weren't doing anything.
    I deleted the chace folder, it was a missing rare etc.
    After it my mate found an another, but the addon were still silent.

    Any advice?
  • #1036
    Have you updated since then? I didn't release the Cataclysm version until just after the US servers came online, so you might have grabbed version if you updated earlier than that.

    If you do have version 4.0.0.x already, it's probably settings related. I haven't seen Old Crystalbark in a while, but I did test scanning on a random Borean Tundra mob and it was detected fine with version Do you have the "Frostbitten" tab's checkbox enabled in your "/scan" settings? Another possibility is this is the second time you've killed Crystalbark, and you have the "Search for completed Achievement NPCs" option enabled; Try turning that off if this is the case.

    I'm not sure about your why your friend would have similar trouble, but it could be one of the above or a cache issue if it was a tamable mob.
  • #1040
    My problem is solved.
    The main issue was that my curseclient didn't update the entire folder so I had a few remaining file from 3.3.5.
    So I deleted my _NPCScan folder and updated the newest release again.
    And voila, it's working again. :)

  • #1030
    I got this error on logging in. As seen by BugGrabber, English client.

    1x :":OnShow":4: attempt to concatenate local 'name' (a nil value)
    : in function `CreateFrame'
    _NPCScan-\_NPCScan.Config.Search.lua:24: in main chunk

    (*temporary) = "Button"
    (*temporary) = nil
    (*temporary) = {
    0 =
    (*temporary) = "GameMenuButtonTemplate"
    (*temporary) = defined =[C]:-1

  • #1059
    What does the cross means lol anyone can tell me
  • #1033
    WoW 4.0.1 isn't compatible with older versions of _NPCScan (you have still), so you'll need to upgrade to the latest version.
  • #1029
    I spent hours trying to find NPC id's and couldn't find: Example, Spirit Beast, Loque'nahak 76 Rare Elite Sholazar Basin . Its not in your current database.

    Is there a way to ADD without a NPC ID to _NPCScan? This is holding me up to add.

    #2: Do you have a current list of NPC ID's that you can make available to download? This would greatly simplify things to add.

  • #1031
    Easy peasy. Just search for the mob by name on Wowhead. Once you're on the mob's individual page, look at the number after the = sign in the URL. That's the NPC id. Here's an example for Loque'nahak. I went to and did a search for Loq. Once I clicked on the NPC page, this is the URL I got: The NPC id is 32517. That's what you put in the NPC ID field. Hope this helps.
  • #1032
    Thank you.

    Wouldn't it be great if there was a downloadable list with all the NPC id codes
  • #1023
    I am currently using the latest version of NPCscan ( and there seems to be a problem that starts to happen after patch. As you may know, hunters have an improvement on their stable slot mechanics, in that they can have 4 "active" pets and 20 "inactive" pets at level 80, tucked inside their stables. Now, even after clearing the cache before logging in, NPCscan seems to auto-detect whatever rares I have inside my "inactive" stable slot as soon as I log into the game (and haven't visited the stables). Of course, if I happen to log in on the zone where the rare is supposed to spawn, the warning siren will turn on. This happens even though I don't have any rares on my "active" pet slots.
  • #1025
    I can confirm this as of right now. I just noticed this on my server as of the new patch. I cleared cache and was sitting in Zul'Drak. As soon as I log in the sound goes off that Gondria is up, now I am sitting near one of the spots so I look around. It was then that I noticed that all of the spirit pets I have in the stables are listed. Was very odd to say the least.
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Marriland Furious Fists Giveaway!