PandaQuest HubGathering nodes
Ore veins, herbs, fishing pools, chests and rare spawns, in the places players have actually gathered them. Pandaria's nodes are in no database this project can reach, so this map exists only because somebody walked over one with the addon on.
Players – where this comes from
Uploaded by players running the addon. Self-reported: nobody verifies it, and it is only as complete as the people who chose to upload. All sourcesPandaQuest – where this comes from
This is an observation computed from players' uploads, not a fact about the game: it carries the sample size it rests on and it changes as more people play. All sourcesNodes are the same on every realm, so the realm picker does not apply here.
Zone and layers
Results
No gathering nodes have been uploaded yet. They appear here once somebody plays with the addon installed, telemetry switched on and the companion syncing – one event per gather, and the map is drawn from those.
What this map is, and what it is not
Players – where this comes from
Uploaded by players running the addon. Self-reported: nobody verifies it, and it is only as complete as the people who chose to upload. All sourcesPandaQuest – where this comes from
This is an observation computed from players' uploads, not a fact about the game: it carries the sample size it rests on and it changes as more people play. All sources- A dot is a place somebody gathered from, not a surveyed point. The coordinate an event carries is where the player stood, which is a couple of yards off and different every time. Gathers within 2% of the zone of each other are one place, drawn at the most frequently reported of those coordinates – a spot a player really stood on, rather than an average of several that nobody did.
- The count counts sightings, not people. One player gathering the same vein forty times is forty sightings. It is the same word the addon's own tooltip uses, and it is never “players”, because counting different uploaders is not something this hub does yet.
- The anonymity gate that covers quest guides does not apply here, and that is a decision rather than an omission. A guide is built from what particular people did, so it is published only once enough different people are behind it. An ore vein is a fact about the game world, identical for every player: what is published here is a coordinate and a count, with no time, no play session, no character name and no ordering that could put a route back together. Somebody who has asked this hub to stop processing their data is left out of the aggregate all the same.
- There is no minimum-skill filter, because there is no skill here to filter on. What players upload is a kind, an object id and a place; a skill requirement is not in it, and this hub does not invent one. The addon's own node list could supply a few – it is pfQuest's, and 109 of its 693 entries name a mining or herbalism skill – but pfQuest is Vanilla and Burning Crusade, so not one of those 109 is a Pandarian node, and the list is not loaded here in any case. A control with nothing behind it quietly matches everything or nothing, so the filter above is by kind alone.
- A respawn is a median of measured intervals, with the sample count beside it. Below 2 measurements there is no respawn line at all – a blank respawn cell beside a node means nobody has measured that one, and is not a zero. A measurement ages out with the event row it came from, so a timer can disappear again with nothing having gone wrong.