Wowhead still shows the same non existent nodes around the dark portal.
The fel iron deposits were gone from the Dark Portal last night, but you're right. They're back now. Wowhead's been updating all day with the number of mining/herbalism nodes generally increasing as time goes by. Not sure what they're up to.
The only problem with scraping wowhead is that wowhead's data still had old pre 2.1 nodes in there which have been moved or removed. Also anyone can submit data to wowhead in fact lots of people spam wowhead with fake data and nodes :(
Wowhead's been pretty accurate for me so far. There's one route in Nagrand I farmed pre 2.1 where I found a node at every pre-populated spot and could not find any that weren't already in Wowhead's database. So personally I haven't seen any indication that people are faking nodes on Wowhead.
Also, it looks like they've updated their mineral locations early this AM because there are no longer any fel iron deposits listed near the black portal. Also, the number of nodes has changed. There's now 11531 which is up 161 over the previous 11370 as per this page.
Quote from priestmaxi »
I dont know if this is a common error now - but when I loaded the DB file, wow crashed when I logged into the game.
Though I got it to work if I changed the place in the .lua file where it says:
version = 3,
- in the old file it was located in the bottom, after the coords, apparently its at the top in the new ones...
Personally, I haven't run into this one yet. Did you try putting the version = 3 at the bottom of the .lua again to prove that it was that line's position that was causing the problem? Is it possible that something else changed about your setup that might have caused it to start working?
I downloaded the DB last night and tried it out on Nagrand. It works great! The only issue I had with it was the overlapping of nodes. It's being overly picky, but I wrote a quick perl script to auto-check wowhead on a daily basis and keep a history of any updates(hopefully wowhead updates soon) and at the same time removing these overlapping mining nodes(4816 overlaps were found). The script just keeps the first node and doesn't add any that are within 0.2 x/y of it. Mining near the pre-populated nodes can possibly put in overlapping nodes, but hopefully it reduces the clutter a little for those that are picky enough to care.