Data extract for GatherMate2. Use GatherMate_Data for the original GatherMate. This version is include data for cataclsym ,as extrernal sites begin migrating their data.

Video about configuring this addon.

How to install the data:

  • 1.) install GatherMate2_Data
  • 2.) Once in game, open gathermate (/gathermate)
  • 3.) Select the Import section
  • 4.) select the data you want and click import.
  • 5.) Profit

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of mysticalos mysticalos Dec 05, 2010 at 08:19 UTC - 0 likes

    you know what, the data on wowhead is tainted by chinese players. just look at EPL or northern STV which clearly as bad data from CN wow showing nodes in 3.x locations. all the 3.x nodes are all over the zone messing it up. i had hoped wowhead would be smarter then that and ignore data. they cleared database but they are just throwing 3.x and 4.x data together. so you really can't trust the data at all :\


    double checking, wowhead actually seems fine for STV, seems the problem is gathermate 2 data, i did overright, it's still putting nodes in bad paces on it's own

    click on northern stv, and look at the sagefish schools in right place, along river, now look at them on gathermate2 in northern STV, it shows them all on land no where near water.. Not sure where the bug is, possiby the parser not knowing difference between zoomed out full STV view, and northern STV view..

    i do suspect a little bit of both issues, wowhead having bad cn data, but also gm2 messing it up too. cause EPL still feels wrong to me. those chests in tyr's are always coming back on wowhead and have been gone forever. heck that's 2.x data right there. and the blood of heroes looks like 3.x data

    Last edited Dec 05, 2010 by mysticalos
  • Avatar of mysticalos mysticalos Dec 05, 2010 at 07:57 UTC - 0 likes

    the big problem is the mac client for wowhead hasn't been updated since like patch 3.0 (literally) and it installs a pretty non functional clint that cannot connectto update server, therefor it cannot install a current version of addon or client (if they even exist) was noting but a nightmare trying to get it to work, and i have a lot of data too. I just literally did EVERY quest in all the 1-60 zones on both continents. found tons of nodes that were in each zone that aren't on wowhead or gm2, and they ddin't get any of them, such a waste :\

    ah edit, they fixed the client on 29th it looks like for mac

    Last edited Dec 05, 2010 by mysticalos
  • Avatar of fixitman fixitman Dec 01, 2010 at 21:51 UTC - 0 likes

    I run WoW on a totally different partition (D:/WOW) under Win7 64bit. I also have UAC turned off (poor implementation of a great idea, IMO). I've had no issues with WowHead Looter. Keep in mind that WowHead Looter doesn't actually "install". It is just a self-contained application that you run.

  • Avatar of Malazee Malazee Dec 01, 2010 at 00:35 UTC - 0 likes

    Having a hard time contributing my data via the wowhead looter since it can't be installed on 64bit OSs (apparently). Anyone know of a workaround? (thread about the 64bit problem)

    Last edited Dec 01, 2010 by Malazee
  • Avatar of fixitman fixitman Nov 29, 2010 at 17:22 UTC - 0 likes

    I believe the overwrite option was just to initially purge old data. If you use the overwrite option every week, it could potentially wipe any new nodes you've found (if the Wowhead database doesn't have them for some reason).

    Last edited Nov 29, 2010 by fixitman: removed unnecesary portion, moved to GM2
  • Avatar of myrroddin myrroddin Nov 29, 2010 at 17:17 UTC - 0 likes

    Additional thought: Pitbull4 has two VisualHeal folders, and VisualHeal5's .toc file has a neat trick forcing it to only load on WoW 4.x clients, and VisualHeal only loads on WoW 3.x ... could that be done with GatherMate / GatherMate_Data (3.x) and GatherMate2 / GatherMate2_Data (4.x)? It might cut down on pollution. Maybe. Hopefully.

  • Avatar of myrroddin myrroddin Nov 29, 2010 at 17:13 UTC - 0 likes

    I'll run the WowHead Looter as often as I can. Hopefully the data isn't polluted on their end by Chinese players, who are still on patch 3.x.x

    Just to be clear; for now, use "overwrite" rather than "merge" for the import? No need for me to dump zones if I have already deleted the saved variables, for someone else, that would work.

    Another thing: when I search WowAce for "gathermate" neither GatherMate2 or GatherMate2_Data show up on the return. To find this page, I had to click Addons at the top and scroll back through the updated addons list. Failing that, find it on Curse and click the link.

  • Avatar of fixitman fixitman Nov 29, 2010 at 12:27 UTC - 0 likes

    I deleted all data for all types via GM2 last night. I then imported GM2_Data v1.6. Eastern Kingdoms and Kalimdor seem to be clean, with all but a few nodes in realistic areas. Northrend still has a huge number of totally wrong node locations for every zone. It took about an hour to manually delete all the obvious ones (nodes over open ocean, out of the zone completely, and stuff like Tiger Lily nowhere near water).

    I've started using the Wowhead client again, just to help the effort. I'm concerned that all my efforts last night will just be wiped out on the next update though. What files do I need to back up in case that happens?

  • Avatar of kagaro kagaro Nov 28, 2010 at 22:06 UTC - 0 likes

    If you wana help cleanup the database install the Wowhead client and help upload data

  • Avatar of kagaro kagaro Nov 28, 2010 at 21:54 UTC - 0 likes

    the WowHead looter is what provides data to wowhead (assumign you actually upload the data afterwards)

    You could set your merge style to overwrite to have it dump zones and reload it for you. A portion of bad data is coming from wowhead where some zones are coming back with old data that shoul dbe the new post sundering data.


Date created
Oct 10, 2010
Last update
Nov 24, 2014
Development stage
All Rights Reserved
Curse link
Recent files
  • A: r387 for 6.0.3 Nov 24, 2014
  • R: v23.8 for 6.0.3 Nov 23, 2014
  • A: r385 for 6.0.3 Nov 23, 2014
  • R: v23.7 for 6.0.3 Nov 16, 2014
  • A: r383 for 6.0.3 Nov 16, 2014



Tool used