PandaQuest HubWhere the data comes from
This site mixes four kinds of knowledge, and they are not equally reliable. Blizzard's artwork is theirs. The quest database is a community project built from server dumps and from Wowhead. Everything about what actually happened was uploaded by players running the addon, and everything this hub says about that is an observation with a sample size, not a fact about the game. Below is each of them, at the version this installation is actually running.
The short version
- The pictures are Blizzard's. Zone maps and item icons are the game client's own artwork, used here the way any fan site uses it. PandaQuest claims no ownership of them, does not sell them, and removes them on request.
- Blizzard’s own API is a different source from Blizzard’s artwork. The Battle.net API is where realm names and the spellings Blizzard’s own URLs use come from, and anything on this site that came from it is Blizzard’s own record rather than something a player typed. Whether this installation reads it at all is the operator’s decision, and the answer here is: not configured The Battle.net API is not configured: PQ_BLIZZARD_CLIENT_ID and PQ_BLIZZARD_CLIENT_SECRET are empty. Create a client at develop.battle.net and put the id and the secret in the hub's environment file. Nothing on this site depends on it: the realm menu is built from the realms players have uploaded, which is what it has always been. The full entry
- What a quest is comes from Questie – a community database built from cmangos server dumps and from Wowhead, generated into the addon and loaded into this hub by its operator. It is the same on every realm and nobody's play changes it.
- What happened comes from the players. Sessions, timings, coordinates and deaths are uploaded by people running the addon. It is self-reported: nobody verifies it, and it is only as complete as the people who chose to send it.
- What we say about it is derived. Routes, medians and leaderboard positions are computed here from those uploads. They carry their sample size wherever they appear, and they change as more people play.
Your own uploads stay yours: export or erase them at any time, and every figure they fed is recomputed without them. What that means in full is in the privacy statement.
Every source
Counted from this installation as this page was rendered (), not read off a list somebody kept up to date by hand. “Not imported” is an answer, and it is the honest one wherever an optional importer has never been run here.
| Source | Whose | Covers | State here | Version | Imported |
|---|---|---|---|---|---|
| Questie – the quest database | Questie | What a quest is: its name and level, what you have to do, what you need to bring, what it gives you, who may take it, and what comes before and after it. Also what the NPCs and objects it names are called – on a quest page and on the node map – and, where Wowhead has not answered for a quest, the experience it pays. | not imported | – | – |
| Questie – the item catalogue | Questie | What an item is: its name, its item level, the level needed to use it, and whether it is a recipe, a trade good, a gem or a glyph – which is what the profession pages count. | not imported | – | – |
| Questie – the object database's gathering nodes | Questie | Which Mists gathering nodes are recorded in which Pandaria zone, on the three gathering professions' pages – the zone only, and never a place inside it. | present | – | – |
| Questie – the NPC database's profession subtitles | Questie | Which NPCs the generated database describes as Archaeology trainers, and the zone and the faction it records for each of them – on the Archaeology page. The names beside them are the imported ones, which is the quest database's row above. | present | – | – |
| Blizzard – zone maps | Blizzard | The zone map drawn behind the objective points, hotspots and death markers. | not imported | – | – |
| Blizzard – item icons | Blizzard | The item and ability icons on quest rewards and on a character's equipment. | not imported | – | – |
| Blizzard – the game's own API | Blizzard | Realm names and their Blizzard spellings, and on a character page Blizzard's record of the character: what it is wearing, its stats and specialisation, the picture of it and the item icons. Auction prices are not built. | not configured | – | – |
| Wowhead – money and experience | Wowhead | The money a quest pays, which no other source this hub can reach has at all, and the experience beside it. Nothing else on this site comes from Wowhead. | nothing fetched yet | – | – |
| Players – what they did | Players | Everything about what actually happened: sessions, quest runs and their timings, coordinates, kills, deaths and turn-ins. | nothing uploaded yet | – | – |
| Players – auction prices | Players | Auction house prices, and your own sale and purchase receipts. | nothing scanned yet | – | – |
| PandaQuest – our own analysis | PandaQuest | Routes, hotspots, median times, objective order, leaderboard positions – everything this hub works out rather than receives. | nothing published yet | – | – |
Questie – the quest database not imported
Questie – where this comes from
This comes from the Questie quest database, the same on every realm and unchanged by anyone playing. All sourcesWhat a quest is: its name and level, what you have to do, what you need to bring, what it gives you, who may take it, and what comes before and after it. Also what the NPCs and objects it names are called – on a quest page and on the node map – and, where Wowhead has not answered for a quest, the experience it pays.
No quest data has been imported into this hub. Quest pages show only what players uploaded – a name, a level and a map – until an operator runs platform/tools/questimport.py.
- Where it came from
- The Questie addon's own quest database, itself built from cmangos server dumps and from Wowhead. Generated into the PandaQuest addon by tools/build_db.py and loaded into this hub by platform/tools/questimport.py; the NPC and object names and the experience figures come out of the same generated files, loaded by platform/tools/entityimport.py. No request to anybody is made for any of it.
- Whose it is
- Questie's data, under Questie's own licence; the game's names and text are Blizzard's. This site is a fan site and neither claims ownership.
Questie – the item catalogue not imported
Questie – where this comes from
This comes from the Questie item database: names, levels and item classes only. It carries no reagents, no recipe results and no prices, and it is the same on every realm. All sourcesWhat an item is: its name, its item level, the level needed to use it, and whether it is a recipe, a trade good, a gem or a glyph – which is what the profession pages count.
No item catalogue has been imported into this hub. The profession pages can count nothing and the auction pages show item ids instead of names until an operator runs platform/tools/itemimport.py.
- Where it came from
- The same generated database as the quest data, built into the PandaQuest addon by tools/build_db.py, and loaded into this hub by platform/tools/itemimport.py.
- Whose it is
- Questie's data, under Questie's own licence; the game's item names are Blizzard's. This site is a fan site and neither claims ownership.
Questie – the object database's gathering nodes present
Questie – where this comes from
This comes from the Questie object database: which gathering node has been seen in which Pandaria zone, and never where in it. It is the same on every realm, and it is a table in this site's own source rather than something an operator imports. All sourcesWhich Mists gathering nodes are recorded in which Pandaria zone, on the three gathering professions' pages – the zone only, and never a place inside it.
20 Mists gathering nodes recorded across 5 Pandaria zones, as a table in this site's own source. Nothing imports it and it is the same on every installation; the zone is all of it, never a place in the zone.
- Where it came from
- PandaQuest/Database/Data/Objects.lua in the same generated database, read once through its spawn areas and written down as a table in this hub's own source (pandaquest_hub/professions.py). It is a handful of zone names rather than something a page queries, so no tool loads it; platform/tests/test_professions.py reads that file and checks the table back against it, both ways for ore and fishing pools.
- Whose it is
- Questie's data, under Questie's own licence; the game's object names are Blizzard's. This site is a fan site and neither claims ownership.
| Measure | Value |
|---|---|
| Mists nodes in this table | 20 |
| Pandaria zones with one | 5 |
Questie – the NPC database's profession subtitles present
Questie – where this comes from
This comes from the Questie NPC database: which NPC it calls an Archaeology trainer, and where it records them standing. It is the same on every realm, and it is a table in this site's own source rather than something an operator imports. All sourcesWhich NPCs the generated database describes as Archaeology trainers, and the zone and the faction it records for each of them – on the Archaeology page. The names beside them are the imported ones, which is the quest database's row above.
21 NPCs the generated database subtitles “Archaeology Trainer”, 2 of them in a Pandaria zone, as a table in this site's own source. 20 of the 21 also carry the trainer bit of the record's npcFlags. Nothing imports it and it is the same on every installation; what it records is the zone, never a place in the zone. The NPC names themselves have not been imported, so the page prints these ids – platform/tools/entityimport.py loads the names out of the same generated file.
- Where it came from
- PandaQuest/Database/Data/Npcs.lua in the same generated database, read once through its subName field (Schema.lua npcKeys field 14) and written down as a table in this hub's own source (pandaquest_hub/professions.py). It is twenty-one rows rather than something a page queries, so no tool loads it; platform/tests/test_professions.py reads that file and checks the table back against it, both ways.
- Whose it is
- Questie's data, under Questie's own licence; the game's NPC names and subtitles are Blizzard's. This site is a fan site and neither claims ownership.
| Measure | Value |
|---|---|
| NPCs subtitled Archaeology Trainer | 21 |
| Of those, in a Pandaria zone | 2 |
| Of those, flagged as a trainer | 20 |
Blizzard – zone maps not imported
Blizzard – where this comes from
The map picture is Blizzard's own artwork, copied into this hub from a mirror of the game's textures and checked against the game client. All sourcesThe zone map drawn behind the objective points, hotspots and death markers.
No zone artwork is served yet, so every map on this site draws an abstract grid instead of the zone, with a sentence under it saying why. Nothing is missing from the data: the coordinates are the same either way. This hub fetches missing zone maps itself, in the background, one zone at a time from the Gethe/wow-ui-textures mirror on GitHub, and only maps whose tiles matched the game client's own. It does so because PQ_MAP_ART_FETCH_ENABLED is on, which is the default on this hub: its user asked for the maps to arrive without anyone running an import. Every map this hub's pages draw has its art.
- Where it came from
- The World of Warcraft client's own map textures, taken from the Gethe/wow-ui-textures mirror on GitHub and stitched into one image per zone -- by this hub in the background, for the maps its pages draw, or by an operator running platform/tools/mapimport.py. Only a copy whose tiles were compared pixel by pixel with the Mists of Pandaria Classic client's own and matched is used. This repository ships none of it.
- Whose it is
- Blizzard Entertainment's artwork, shown here by a fan site. Not ours, not licensed to us, and removed on request.
| Measure | Value |
|---|---|
| Automatic import | on (PQ_MAP_ART_FETCH_ENABLED) |
| Maps the pages draw that have no art | 0 |
| Being fetched | 0 |
| Waiting to retry after a failure | 0 |
| No copy matches the game client | 0 |
Blizzard – item icons not imported
Blizzard – where this comes from
The icon is Blizzard's own artwork; only the icon's name comes from the addon. All sourcesThe item and ability icons on quest rewards and on a character's equipment.
No item icons have been imported. Rewards and equipment are shown by name; the icon's name still comes from the addon, but there is no picture to draw.
- Where it came from
- The same texture mirror as the map art, fetched by platform/tools/mapimport.py --icons-from FILE, where FILE names the icons one per line.
- Whose it is
- Blizzard Entertainment's artwork, shown here by a fan site.
Blizzard – the game's own API not configured
Blizzard – where this comes from
This is Blizzard's own record rather than anything a player typed, and where it describes a character it is as of that character's last logout rather than live. All sourcesRealm names and their Blizzard spellings, and on a character page Blizzard's record of the character: what it is wearing, its stats and specialisation, the picture of it and the item icons. Auction prices are not built.
The Battle.net API is not configured: PQ_BLIZZARD_CLIENT_ID and PQ_BLIZZARD_CLIENT_SECRET are empty. Create a client at develop.battle.net and put the id and the secret in the hub's environment file. Nothing on this site depends on it: the realm menu is built from the realms players have uploaded, which is what it has always been.
- Where it came from
- Blizzard's own Battle.net API, read by this hub with credentials its operator created at develop.battle.net. Nothing is fetched while a page is being rendered: an operator runs `pq-hub blizzard realms --apply`, a character is refreshed in the background after its player uploads or when its owner presses "Refresh from Blizzard", and the pictures are copied onto this hub and served from it.
- Whose it is
- Blizzard Entertainment's data, used under the Battle.net Developer API Terms of Use by a fan site that neither sells it nor advertises against it. World of Warcraft is a trademark of Blizzard Entertainment, Inc. in the U.S. and/or other countries.
Wowhead – money and experience nothing fetched yet
Wowhead – where this comes from
Money and experience are read from the quest's Wowhead page in the background; until that answer arrives the page says what is happening rather than showing zero. All sourcesThe money a quest pays, which no other source this hub can reach has at all, and the experience beside it. Nothing else on this site comes from Wowhead.
No quest on this site shows a money or experience figure from Wowhead yet; those fields say so in words rather than showing zero. This hub has no contact address to put in its requests to Wowhead, so it does not send any. The operator sets one with PQ_WOWHEAD_CONTACT.
- Where it came from
- Each quest's own wowhead.com/mop-classic page, read by this hub in the background for the quests people open here and the quests players have run: one page at a time, at most one request every few seconds and a fixed number a day, and each answer kept rather than asked for again.
- Whose it is
- Wowhead's pages are Wowhead's; the underlying game data is Blizzard's.
| Measure | Value |
|---|---|
| Quests with money or experience | 0 |
| Quests answered by Wowhead | 0 |
| Quests waiting | 0 |
| Quests with an experience figure from any source | 0 |
Players – what they did nothing uploaded yet
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 sourcesEverything about what actually happened: sessions, quest runs and their timings, coordinates, kills, deaths and turn-ins.
Nobody has uploaded anything yet. Every community figure on this site is empty until someone plays with the addon on and the companion uploads it.
- Where it came from
- The PandaQuest addon records it while you play; the companion uploads the saved variables file to this hub. Nothing is collected without the addon installed.
- Whose it is
- The players' own uploads. They remain the uploader's, they can be exported and erased at any time, and they are published only in aggregate.
- Removing your own
- Sign in and use your data page: export takes a copy, erasure deletes your uploads and recomputes every guide they contributed to. Your data · what is kept, and for how long
Players – auction prices nothing scanned yet
Players – where this comes from
Player scans uploaded by the companion; community figures are medians over whole UTC days, never with a date. All sourcesAuction house prices, and your own sale and purchase receipts.
No community prices yet. Prices are published by a rebuild that runs once a UTC day, so a house that has just been scanned for the first time appears at the next one – absent, not zero.
- Where it came from
- Auction house scans uploaded by players running the addon, with a consent of their own (docs/08). A community figure is the median of the *people* who scanned, taken over whole UTC days: one person scanning six times an evening weighs exactly as much as one person scanning once.
- Whose it is
- The players' own uploads, on the same terms as the rest of their telemetry.
- Removing your own
- Sign in and use your data page: withdrawing the auction consent deletes your scans and your price history, and every auction house you contributed to has its community prices taken down and rebuilt without you. Your data · what is kept, and for how long
PandaQuest – our own analysis nothing published yet
PandaQuest – 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 sourcesRoutes, hotspots, median times, objective order, leaderboard positions – everything this hub works out rather than receives.
No guides have been published yet. A guide is published from the first recorded run and sharpens with every upload; where players died is added once at least 5 different characters from at least two different people have done the quest. Counts and medians shown elsewhere are computed live from the uploads and always carry their sample size.
- Where it came from
- This hub's own analysis of the players' uploads.
- Whose it is
- Computed here from the sources above; the underlying uploads stay the players'.
- Removing your own
- Erasing your uploads removes your runs from every figure here; the guides they fed are recomputed without them. Your data · what is kept, and for how long
How to read a number on this site
Every figure computed from players' uploads is an observation, and it is printed with the evidence it rests on – the number of runs, characters or scans behind it. A median over three runs is one player's evening; a median over three hundred is a route. The site never hides the difference, and it never fills a gap with a zero: a figure that cannot be computed is shown as unavailable.
PandaQuest – 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 sourcesA quest's guide is published from the first recorded run and sharpens with every upload after it: pick-up, hand-in and the objective hotspots are where the quest is, so one run of them already helps the next player. Where players died is about the player rather than the quest, so the death map waits until at least 5 characters from at least two different people have done the quest. It is the same rule the privacy statement describes.
This is a fan site
PandaQuest is not affiliated with, endorsed by or sponsored by Blizzard Entertainment. World of Warcraft, Mists of Pandaria and the artwork shown here are Blizzard's trademarks and copyrighted material, used by a fan project. The addon, this hub and the analysis of the players' uploads are the project's own work.
Anything on this site that came from the Battle.net API – realm names and their Blizzard spellings, and on a character page Blizzard's picture of the character, its equipment and its stats – is Blizzard Entertainment's data, read under the Battle.net Developer API Terms of Use by a fan site that neither sells it nor advertises against it. It is stored here for at most thirty days before being fetched again, which is what those terms require of anyone keeping it. This installation is not reading that API at all: not configured.
Questie is a separate community project with its own authors and licence, and Wowhead is a separate site; neither has any part in running this hub. If you believe something here should not be published, the terms name who to contact.