This project is abandoned and its default file will likely not work with the most recent version of World of Warcraft. Whether this project is out of date or its author has marked it as abandoned, this project is no longer maintained.
Database dump for GatherMate
Data is gathered from several sources, including user submitted data.
Can somone explain the format for the data. i get for example that [720] = { [5926686700] = 461, the "[720]" bit is the zone i think The bit after the "=" is the herb, in this case 461 = whiptail but how does the big number translate into x,y co-ordinates?
Don't go to the site listed above by user cto0evezipz, it's a spambot! I'm reporting it. If you see it posted on other pages, I suggest reporting it also.
Is there anyway to remove the circles in the mini-map while i'm following a prepared route? I have no need to know where a spawn point is if it doesn't contain an active node, and i have a hard time seeing the yellow indicator that an active node is available.
I'm a newbie here (and in almost everything not involving chemistry, firearms or teaching) and I was wondering if there is a way to recover all of the data I lost from the original Gathermate?
I'm sure that this has been answered, but give a middle-aged fat guy a break :)
Theres a lot of duplicate information in this database. For each node there are 2-3 entries. Often it will show like Icethorn two or three times in the exact same spot, creating 2-3 circles. Cleanup dont help
Yes same issue. I really like Gathermate overall but seeing for example wild steelbloom in the middle of the ocean makes no sense. I tried the clean up as well to merge the data. Every time I update I ended up doing a lot of clean up by hand. Additionally if there are errors such as these what other errors are there or what is missing?
The problem is not with the addon itself, it's with where it's getting the data from - Wowhead.
The Wowhead mineral and herb databases have become polluted with many rubbish data points, and are now almost useless. (IMHO). Even if you clean them up by removing points outside the zone boundaries there are still many false data points left.
There should only be 6 data points for Adamantite Deposit on the Isle of Quel'Danas, that's all the spawn points in that zone. Wowhead lists 19, some of them in the sea.
I don't know what the solution is to this, I can't see any easy way to remove the bad data. For myself, I went back to version 1.90 of Gathermate_Data, which was, I believe, the last one that used data from WoWDB, before that site stopped updating. It's not complete or totally up-to-date, but at least it's clean data and a good starting point.
Hello, Can anyone explain to me why i don't see ANY nodes on main map? Every node that i find in game is marking on my map, but i don't see those from gathermate_data file. I've downloaded, updated and do whatever i had to do. Any ideas, plz tell me.
Hmm...Even though I probably need not worry because I am using a smartphone based authenticator, perhaps you can provide further peace of mind for me too regarding this file format as I could so use this addon right now? Here is what I have read:
YAML allows language specific tags so that arbitrary local objects can be created by a parser that supports those tags. Any YAML parser that allows sophisticated object instantiation to be executed opens the potential for an injection attack. According to the PyYAML documentation:
Note that the ability to construct an arbitrary Python object may be dangerous if you receive a YAML document from an untrusted source such as the Internet. The function yaml.safe_load limits this ability to simple Python objects like integers or lists.
I can confirm that there is SOMETHING wrong here. Haven't had a problem in forever, don't go to phishing sites or emails. Downloaded this last night, woke up this morning with my password changed both in WoW and to my related Gmail account. This might be something that snuck in with a recent version, but for now I caution you to be very careful here.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I just upgraded to a MAC. Is there a trick to get the data to import. on my PC the import just worked but on the mac it is like the file is not there
[720] = {
[5926686700] = 461,
the "[720]" bit is the zone i think
The bit after the "=" is the herb, in this case 461 = whiptail
but how does the big number translate into x,y co-ordinates?
Hi folks.
I'm a newbie here (and in almost everything not involving chemistry, firearms or teaching) and I was wondering if there is a way to recover all of the data I lost from the original Gathermate?
I'm sure that this has been answered, but give a middle-aged fat guy a break :)
Thrackmoor
I stumbled on GatherMate2_Data purely by accident when looking at Routes. The data package is not showing up in any variety of search I tried.
http://www.wowace.com/addons/gathermate2_data/
Hi I was looking for a new version for Gathermate2-Data. Searching was not found
The Wowhead mineral and herb databases have become polluted with many rubbish data points, and are now almost useless. (IMHO). Even if you clean them up by removing points outside the zone boundaries there are still many false data points left.
Example: http://www.wowhead.com/object=181556
There should only be 6 data points for Adamantite Deposit on the Isle of Quel'Danas, that's all the spawn points in that zone. Wowhead lists 19, some of them in the sea.
I don't know what the solution is to this, I can't see any easy way to remove the bad data. For myself, I went back to version 1.90 of Gathermate_Data, which was, I believe, the last one that used data from WoWDB, before that site stopped updating. It's not complete or totally up-to-date, but at least it's clean data and a good starting point.
Can anyone explain to me why i don't see ANY nodes on main map? Every node that i find in game is marking on my map, but i don't see those from gathermate_data file.
I've downloaded, updated and do whatever i had to do. Any ideas, plz tell me.
YAML allows language specific tags so that arbitrary local objects can be created by a parser that supports those tags. Any YAML parser that allows sophisticated object instantiation to be executed opens the potential for an injection attack. According to the PyYAML documentation:
Note that the ability to construct an arbitrary Python object may be dangerous if you receive a YAML document from an untrusted source such as the Internet. The function yaml.safe_load limits this ability to simple Python objects like integers or lists.