10/9/19: Now supports Classic with the most recent data from WoWHead.
BfA 8.2 Update 7/8/19: Added support and data for new 8.2 nodes. Custom Nodes now supported by Gathermate should have their nodid automatically updated in the Gathermate DB
BfA Update 8-16: WoWGatheringNodes now has BfA data.
Now has the ability to import herb & mine data into Carbonite.
WoWGatheringNodes is a data importer for Gathermate2, Carbonite and Gatherer. It currently includes up to date data points for the following objects:
- Mining Nodes
- Herb Bushes
- Archeology Sites
- Lumber
- Gas Nodes
- Fishing Pools
- Various Treasure and Containers
It also has the ability to inject additional objects into Gathermate, Carbonite & Gatherer to allow data for additional object types not currently supported natively by those addons. Currently it adds support for:
- Hidden Wyrmtouge treasures.
- BfA Treasure Chests
- BfA Supply Drop Chests
- 8.2 Resourses
BfA "Rich Osmenite Deposit"
BfA "Osmenite Seam"
BfA "Osmenite Deposit"
BfA "Zin'anthid"
BfA "Mechanized Chest"
BfA "Glimmering Chest"
With additional objects being worked on.
Note: WoWGatheringNodes must be enabled for the injected objects to be shown.
To use,
you just need to enable WoWGatheringNodes, open Gatherer/Carbonite/Gathermate's option menu and select the WoWGatheringNodes Import area. For detailed instructions go here
Or set the Auto Import functionality and the addon will auto import new data when it finds an database update.
The import WowgatheringNodes button for gathermate is greyed out, does that means that there is an issue or that it is up to date?
does this work for gatherlite in classic?
Thanks to everyone for all the answers, awesome comunity!!!
In reply to drumsfanatic:
How did this get fixed? I'm having the same problem
.
Ho do I import data for classic? When i go to the import label in ghatermate2, I can only choose the other expansions of the game but not classic. I can choose:The burning crusade,, Cataclysm, Legion, etc, but not classic. Can you help me please?
Same here :/
Do we have to pick BC or LK and that's fine ?
thx for classic update!
Un´Goro dirt Pile spots dont work, can you fix it?
WoW Classic version, huge question mark :D
In reply to ultromanthetacoman:
Finally had time to update a version for classic.
In reply to SLOKnightFall:
Much obliged, kind sir <3
Do not add the nodes of Nazjatar herbalism in carbonite, does anyone know what to do?
One question, how can you rename a route?
So I was trying to make some routes in Naz (Herbs in this case) and its not creating the routes. It wont make any routes at all. I updated to the latest version.
These are the errors Im getting:
1)
Message: Interface\AddOns\Routes\Routes-v1.6.3.lua:2548: table index is nil
Time: Mon Jul 8 21:29:48 2019
Count: 1
Stack: Interface\AddOns\Routes\Routes-v1.6.3.lua:2548: table index is nil
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:50: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:48>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:789: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:610>
[C]: ?
...face\AddOns\Decursive\Libs\AceGUI-3.0\AceGUI-3.0.lua:71: in function <...face\AddOns\Decursive\Libs\AceGUI-3.0\AceGUI-3.0.lua:69>
...face\AddOns\Decursive\Libs\AceGUI-3.0\AceGUI-3.0.lua:285: in function `Fire'
...sive\Libs\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:22: in function <...sive\Libs\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:19>
Locals: <none>
2)
Message: Interface\AddOns\Routes\Routes-v1.6.3.lua:2548: table index is nil
Time: Mon Jul 8 21:36:59 2019
Count: 21
Stack: Interface\AddOns\Routes\Routes-v1.6.3.lua:2548: table index is nil
Locals: <none>
In reply to jargerwolf:
I'm trying to do the same thing. I get the following error. I also posted in the Routes addon section, the author there seems to thing that WoWGatheringNodes is misbehaving.
53x Routes\Routes-v1.6.3.lua:2548: table index is nil
Routes\Routes-v1.6.3.lua:2548: in function <Routes\Routes.lua:2527>
[C]: ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0-73.lua:50: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:48>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0-73.lua:789: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:610>
[C]: ?
...faceAltoholic\libs\AceGUI-3.0\AceGUI-3.0-36.lua:71: in function <...faceAltoholic\libs\AceGUI-3.0\AceGUI-3.0.lua:69>
...faceAltoholic\libs\AceGUI-3.0\AceGUI-3.0-36.lua:285: in function `Fire'
...olic\libs\AceGUI-3.0-36\widgets\AceGUIWidget-Button.lua:22: in function <...olic\libs\AceGUI-
In reply to Bacrdimike:
I looked at the issue and based on the Routes code, the error appears to be from it not getting localization data for custom nodes. Now that I am aware of the issue and have a idea as to what the problem is i can get a fix out. If all goes well I hope to get it fixed in the next version with the new gathermate fixes.
In reply to SLOKnightFall:
Thank you SLO, from those of us who live and die by our routes addon, we appreciate anything you can do to help get that working again.
Note that over on the routes comment section someone's posted a patch that, in essence, removes the custom nodes from WoWGatheringNodes, and identifies that Gathermate2 has the appropriate data in it already, but the patch basically simply seems to remove the new nodes from Nazjatar's area and replaces it with nothing. With the patch we can't even select nodes in Routes to make a route by, the nodes don't exist in WoWGatheringNodes database anymore. :)
Thanks for the effort to look at the routes addon and add fixes/updates to your stuff to assist.
In reply to Illydth:
No worries and I'm sorry that it was causing issues with Routes. I tracked down the issue and I accidentally flipped the results for a check to see if Routes was enabled, so the part of the addon that should have been providing Routes with the localization data for custom nodes was not actually being loaded. :/ A fixed version should be out later this evening once I get it updated for the new version of Gathermate and a refresh of the node data.
In reply to SLOKnightFall:
Thank you so much for the timely fix! AWESOME!