NPCSCAN problems

[Sukurachi]

ok, so is this addon crap?
I've been camping Madexx, in the hopes of finding the black one. When I look at NPCSCAN the black, brown and green models are already cached as having been found. This is no matter how many times I clear the cache in WoW. And I know it isn't because some passing hunter has a Madexx of that colour out... I'm alone, in the middle of nowhere.

I even tried deleting the black Madexx from the list and re-adding it, and still, it appears with the little "x" next to it, and greyed out.

I'm running WinXP, so no problems with hidden files or anything. I KNOW I'm deleting the right file. Or do I absolutely have to delete the entire cache folder?

[Andine]

The add-on does have its problems. It says to remove an NPC from cache you need to type /npcscan remove (name), but when I do that, all it says is "(name) not found" - for ALL NPCs.

[Serenith]

When something gets cached for me, and I want to make sure it will go boom, I just delete the file in the WoW cache called "creaturecache.wdb". Perhaps you aren't clearing it completely? I use a Mac so I can't talk you through Windows filing systems. =(

But yeah, after I delete that file nothing will be cached.

[Sukurachi]

As I said, I AM deleting the creature_cache file (whatever its proper name is).

And no matter what I do, those three particular Madexx colours remain cached, along with a number of other mobs... some of which I KNOW I've never seen (there aren't hunter pets, and I haven't spent enough time in the area to have come across them).

[Kalliope]

Did you close out of WoW before deleting?

[Sukurachi]

Yup, turned everything off, deleted, then restarted...

AND...
I seem to have solved the problem.

It would appear that NPCSCAN doesn't only look in WoW's /Cache folder for the creaturecache.wdb file.

It would seem that I had a backup of the cache folder on another drive (my computer has multiple hard drives), and somehow, NPCSCAN looked everywhere to find a copy of creaturecache.wdb.

After deleting every single instance of creaturecache.wdb, including those in my Recycle Bin, it FINALLY works properly.

[Sesamee]

When I want to make sure I clear out a cache I go to the zone I'm looking for a mob in, exit game, and delete BOTH folders in the WoW Cache file. Then I log back in and it's fine. Also make sure you have npcscan set to only show the paths of mobs you're looking for, that way if the path doesn't show up on the map, you know something's wrong. You can turn this on and off easily by going to the search tab, I leave it off most of the time.

[Serenith]

After deleting every single instance of creaturecache.wdb, including those in my Recycle Bin, it FINALLY works properly.

Well, at least its working now. I think I can recall a time my BF had a similar issue where he deleted it from the rightful place, but there was another file somewhere and it drove him crazy before he found it.

[Bryndell]

I always empty the recycle after deleting, just in case.

[Lazurianis]

Bear in mind, NPCScan has its problems yes but cacheing in NPC Means you have already found it, (Being Tamed or dead it doesnt matter) sometimes NPCScan will still alert you it is there, however just grab SilverDragon, it always alerts you when a Rare is near, it is a bit buggy, i've been in Stormwind before and it alerts me that I found Deathmaw (A Rare in Burning Steppes) so if it says "Level: ?+" it means its bugged, dont sweat it. >HOWEVER< It will do this for Level ?? Rare Bosses so if its an NPC that makes no sense for, stick to what I said earlier.

[Kurasu]

Bear in mind, NPCScan has its problems yes but cacheing in NPC Means you have already found it, (Being Tamed or dead it doesnt matter) sometimes NPCScan will still alert you it is there, however just grab SilverDragon, it always alerts you when a Rare is near, it is a bit buggy, i've been in Stormwind before and it alerts me that I found Deathmaw (A Rare in Burning Steppes) so if it says "Level: ?+" it means its bugged, dont sweat it. >HOWEVER< It will do this for Level ?? Rare Bosses so if its an NPC that makes no sense for, stick to what I said earlier.

The thing with SilverDragon is that it works in a number of different ways. One of these is from cache. If it's not grabbing from the cache, you need to be close enough to see the monster's name for SilverDragon to be able to 'react' to it.

I use both NPCScan and SilverDragon together as they have different advantages. SilverDragon will, indeed, catch rares that NPCScan isn't programmed for (or even *it* doesn't have programmed in) because it reacts to the 'silver dragon' itself. Also, SilverDragon will find them even if cache is full if you have 'mouseover' or 'nameplate' enabled, and get close enough to either mouse over or see the nameplate. However, SilverDragon isn't customizable like NPCScan is to find things that aren't rares. So, long as you don't mind potentially two warnings coming up for some of the rares, I find it worth it to run with both going.