Where 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. PandaBase 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: present 34 realms fetched from Blizzard's own realm index, and Blizzard's record of 3 characters -- profile, equipment, stats, specialisation -- with 66 pictures copied onto this hub, so no page links to Blizzard's servers. Held for at most 30 days and then re-fetched, which is what the Battle.net API terms require of anyone storing their data. Last fetched . 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. | present | Questie 12.9.0+v1.1.1 | |
| 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. | present | Questie 12.9.0+v1.1.1 | |
| 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 – the game client's profession tables | Blizzard | What a recipe makes and what it consumes, the skill it asks and the skill levels at which it turns yellow, green and grey, what teaches it, and the icons – on every profession page. Also Archaeology's races and projects. | present | wow_classic 5.5.4.70032 | – |
| Blizzard – the game client's creature and faction tables, with the NPC database | Blizzard | What kind of creature an NPC is (Humanoid, Beast, Battle Pet ...), whether it is elite, rare or a boss, its levels and title, how it treats the Alliance and the Horde, and the zones it stands in – on the NPC list and each NPC's page. | present | Questie 12.1.0+v1.0.6; wow_classic 5.5.4.70032 | |
| Blizzard – the game client's item tables, ranked by stat weights (best in slot) | Blizzard | Every item on the best-in-slot pages: its name, quality, level, slot, stats, sockets and where it comes from (a boss, a profession, a PvP season or a currency), the enchants, gems and consumables beside them, and the class and specialisation names. | present | wow_classic 5.5.4.70032 | – |
| Blizzard – the game client's flight paths | Blizzard | On the flight routes page: every flight point and which side may use it, which direct flights the game has between them, the base price of each and the path the taxi flies, from which an untimed flight's length is measured. | present | wow_classic 5.5.4.70032 | – |
| Blizzard – zone maps | Blizzard | The zone map drawn behind the objective points, hotspots and death markers. | present | – | |
| Blizzard – item icons and map markers | Blizzard | The item and ability icons on quest rewards and on a character's equipment, the Alliance, Horde and Pandaren crests beside a quest or a character, and every marker on the maps -- the quest giver's “!” and the hand-in's “?”, flight paths, innkeepers, trainers and the other services, rares, deaths and gathering nodes. | present | – | |
| 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. | present | – | |
| Blizzard – the 3D figures, from the game client's files | Blizzard | The 3D figure on a character sheet and on a best-in-slot list: the race's model, dressed in the items, the face, the skin and the hair the record names, standing as the game's character frame shows it. The 3D model on an NPC's page, and the small picture of it a link to the NPC shows when the pointer rests on it: the creature the game draws the NPC as, in its own skins, or -- for an NPC on a playable race's body -- that race dressed and groomed as the game's tables say the NPC is. | present | – | – |
| Wowhead – money, experience, item details, sell prices and the database's gaps | Wowhead | The money a quest pays, which no other source this hub can reach has at all, and the experience beside it. From the same page, and only where the quest database has nothing: the quest's reward items, its objective line and who starts and ends it, Wowhead's note that Blizzard marked a quest obsolete, the quest giver's text and the places Wowhead's map of the quest marks. An item's details -- quality, item level, binding, slot, stats, sockets, set, requirements, effects -- and its vendor sell price, read off the item's Wowhead tooltip. An NPC's or an object's level, type, reaction, faction and health, where it stands, what it sells and for how much, what it drops or contains and how often, and the number of the creature display an NPC is drawn by (the figure itself is drawn here, from the game's files). No picture comes from Wowhead, and nothing else on this site does either. | present | – | |
| Moderators – corrections to the quest database | Moderators | Corrections a moderator or an admin of this site made by hand to a quest, an NPC, an object or an item -- a name, a level, the objective text, who starts or ends a quest, where an NPC stands -- and what they added that no import has, or took off because it is not in the game. | no corrections yet | – | – |
| Players' suggestions – corrections a moderator approved | Players' suggestions | Corrections, additions and removals a signed-in player suggested from a quest's page and a moderator approved and applied. | no approved suggestions yet | – | – |
| Players – what they did | Players | Everything about what actually happened: sessions, quest runs and their timings, coordinates, kills, deaths and turn-ins, and the flights taken from a flight master with how long each took and what it cost. | present | – | – |
| PandaQuest – our own analysis | PandaQuest | Routes, hotspots, median times, objective order, leaderboard positions, flight times – everything this hub works out rather than receives. | present | – |
Questie – the quest database present
This comes from the Questie quest database, the same on every realm and unchanged by anyone playing.
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.
11,362 quests imported into this hub from Questie 12.9.0+v1.1.1. Quests the addon hides – removed from the game or never implemented – are not imported, because the addon never offers them.
- 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.
- Version
- Questie 12.9.0+v1.1.1
- Imported
| Measure | Value |
|---|---|
| Quests in this hub | 11,362 |
| NPC and object names | 79,590 |
| Quests with an experience figure from Questie | 10,366 |
Questie – the item catalogue present
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.
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.
80,049 items imported into this hub from Questie 12.9.0+v1.1.1. Five columns of each: name, item level, required level, item class and subclass. The generated database has no reagent field and no link from a recipe to what it teaches, so this catalogue cannot say what anything is made of; the profession pages take that from the game client's own tables, which have their own row.
- 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.
- Version
- Questie 12.9.0+v1.1.1
- Imported
| Measure | Value |
|---|---|
| Items in this hub | 80,049 |
Questie – the object database's gathering nodes present
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.
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.
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
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.
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.
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.
- 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 – the game client's profession tables present
This is read from the game client's own tables. The client has no trainer table and no gathering-node loot, so who teaches a recipe, what a node asks and where it stands are not here.
What a recipe makes and what it consumes, the skill it asks and the skill levels at which it turns yellow, green and grey, what teaches it, and the icons – on every profession page. Also Archaeology's races and projects.
5,320 recipes of 15 professions, 8,831 items and 2,808 icons read from the game client (wow_classic 5.5.4.70032), as a file in this site's own source. Nothing imports it and it is the same on every installation. Not in the client's tables: trainers and where a recipe is learned from one; the required skill of most trainer recipes; a gathering node's required skill, loot and spawn points; item sources and prices.
- Where it came from
- The World of Warcraft Classic client's own DB2 tables (SkillLineAbility, SpellEffect, SpellReagents, ItemSparse, ItemEffect and others), as wago.tools publishes them, read once by platform/tools/professions.py for one client build and committed as platform/web/data/professions/mop.json. This hub only reads that file; nothing is fetched while a page is served.
- Whose it is
- Blizzard Entertainment's data, extracted from the game client and shown here by a fan site. Not ours, not licensed to us, and removed on request.
- Version
- wow_classic 5.5.4.70032
| Measure | Value |
|---|---|
| Recipes | 5,320 |
| Items it names | 8,831 |
| Icons the pages draw | 2,808 |
Blizzard – the game client's creature and faction tables, with the NPC database present
This is read from the game client's own tables and the Questie NPC database; a fact neither has is filled in from the NPC's Wowhead page once a page here has shown it.
What kind of creature an NPC is (Humanoid, Beast, Battle Pet ...), whether it is elite, rare or a boss, its levels and title, how it treats the Alliance and the Horde, and the zones it stands in – on the NPC list and each NPC's page.
60,224 NPCs. The type of 1,827 comes from the client's own table and of 13,760 from their Wowhead pages; 44,637 have no known type yet. The classification of 1,827 is the client's and of 58,244 the NPC database's. The reaction of 55,660 is worked out from the client's faction templates and of 368 read off Wowhead; 4,196 name no faction.
- Where it came from
- The World of Warcraft Classic client's Creature, CreatureType and FactionTemplate tables, as wago.tools publishes them, merged by platform/tools/npcfacts.py with the levels, rank, title, faction and spawns of the Questie NPC database (Npcs.lua). The client wins where it lists an NPC; the reaction is the game's own faction-template rule applied to the NPC's faction; a moderator's spawn correction wins over the zones; and what this hub read off an NPC's Wowhead page fills only what the other two leave empty – the type, mostly, because the client lists fewer than two thousand of the sixty thousand NPCs.
- Whose it is
- Blizzard Entertainment's data, extracted from the game client, and Questie's data under Questie's own licence. This site is a fan site and claims neither.
- Version
- Questie 12.1.0+v1.0.6; wow_classic 5.5.4.70032
- Imported
| Measure | Value |
|---|---|
| NPCs with facts | 60,224 |
| Type known | 15,587 |
| Reaction known | 56,028 |
Blizzard – the game client's item tables, ranked by stat weights (best in slot) present
Item names, levels, stats and sources are read from the game client's own tables. The order is this site's ranking by stat weights, not a simulation, and a source is a kind of place: the client has no drop chances, so none are shown.
Every item on the best-in-slot pages: its name, quality, level, slot, stats, sockets and where it comes from (a boss, a profession, a PvP season or a currency), the enchants, gems and consumables beside them, and the class and specialisation names.
34 specialisations of 11 classes, 3,673 items read from the game client (wow_classic 5.5.4.70032), as a file in this site's own source; 3 of 34 specialisations have been reviewed by a person and the rest are ordered by stat weights alone. Nothing imports it and it is the same on every installation. The stat weights were read from Icy Veins, Warcraft Tavern. Not in the client's tables: drop chances; vendors and prices; which content was live and when; trinket, weapon enchant and meta gem effects; reforging and item upgrade steps; Death Knight rune enchants.
- Where it came from
- The World of Warcraft Classic client's own DB2 tables (ItemSparse, JournalEncounterItem, SpellItemEnchantment, GemProperties and others), as wago.tools publishes them, read once by platform/tools/bis.py for one client build and committed as platform/web/data/bis/mop.json. The order of a list is a weighted sum of an item's stat amounts; the weights per specialisation are written down in platform/tools/bis_weights.json and credited, on every page, to the guides they were read from and the day they were read. The hub only reads the file; nothing is fetched while a page is served. An admin can correct a list by hand -- put an item first, add one, leave one out -- on top of the file; a page says how many such changes it carries and marks the rows placed by hand.
- Whose it is
- Blizzard Entertainment's data, extracted from the game client and shown here by a fan site: not ours, not licensed to us, and removed on request. The weights are facts about what a guide said on a day, not copies of its text, and are this site's own ranking: it is not a simulation and no guide has endorsed it.
- Version
- wow_classic 5.5.4.70032
| Measure | Value |
|---|---|
| Specialisations | 34 |
| Reviewed | 3 of 34 |
| Items it names | 3,673 |
Blizzard – the game client's flight paths present
Flight points, direct flights, prices and paths are read from the game client's own tables. How long a flight takes is not in them: that is what players' addons time.
On the flight routes page: every flight point and which side may use it, which direct flights the game has between them, the base price of each and the path the taxi flies, from which an untimed flight's length is measured.
335 flight points and 1,632 direct flights read from the game client (wow_classic 5.5.4.70032), as a file in this site's own source; 333 of the flight points have their flight master matched. Nothing imports it and it is the same on every installation.
- Where it came from
- The World of Warcraft Classic client's own DB2 tables (TaxiNodes, TaxiPath and TaxiPathNode, with UiMap and UiMapAssignment to place them), as wago.tools publishes them, read once by platform/tools/taxigraph.py for one client build and committed as platform/web/data/flights/mop.json. Each flight point's flight master is matched from the addon's NPC data by where they stand. The hub only reads the file; nothing is fetched while a page is served.
- Whose it is
- Blizzard Entertainment's data, extracted from the game client and shown here by a fan site. Not ours, not licensed to us, and removed on request.
- Version
- wow_classic 5.5.4.70032
| Measure | Value |
|---|---|
| Flight points | 335 |
| Direct flights | 1,632 |
| With their flight master | 333 |
Blizzard – zone maps present
The map picture is Blizzard's own artwork, drawn from the game client's files, or copied from a mirror of the game's textures and checked against the game client.
The zone map drawn behind the objective points, hotspots and death markers.
533 zone maps served. Blizzard's artwork, held by this hub and served from here. 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. Of the maps this hub's pages draw, 17 have no art: 0 being fetched, and 17 with no copy that matches the game client, which stay a grid rather than a picture that could put the markers in the wrong place.
- Where it came from
- The World of Warcraft client's own map textures, read from the game client's files through wago.tools by an operator running platform/tools/clientmaps.py and drawn the way the game draws a fully explored map: the base map with every discovered area's picture, and the place names painted into it, on top. A map that tool has not drawn may come from the Gethe/wow-ui-textures mirror on GitHub instead, stitched into one image per zone by this hub in the background or by an operator running platform/tools/mapimport.py -- and only a copy whose tiles were compared pixel by pixel with the Mists of Pandaria Classic client's own and matched. 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.
- Imported
| Measure | Value |
|---|---|
| Zones with artwork | 533 |
| Last map arrived | 2026-10-28 05:36 UTC |
| Automatic import | on (PQ_MAP_ART_FETCH_ENABLED) |
| Maps the pages draw that have no art | 17 |
| Being fetched | 0 |
| Waiting to retry after a failure | 0 |
| No copy matches the game client | 17 |
| Fetched from | github.com/Gethe/wow-ui-textures |
Blizzard – item icons and map markers present
The icon is Blizzard's own artwork; only the icon's name comes from the addon.
The item and ability icons on quest rewards and on a character's equipment, the Alliance, Horde and Pandaren crests beside a quest or a character, and every marker on the maps -- the quest giver's “!” and the hand-in's “?”, flight paths, innkeepers, trainers and the other services, rares, deaths and gathering nodes.
9,853 icons imported. Blizzard's artwork, served from this hub. The maps draw 35 of their 35 markers with the game's own pictures.
- 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. The faction crests are the game client's own (Interface/FriendsFrame/PlusManz-Alliance and PlusManz-Horde, Interface/Timer/Panda-Logo), drawn by platform/tools/clienticons.py --file-ids-from platform/tools/faction_icons.txt. The map markers are the game client's own minimap and world-map pins (Interface/Minimap/ObjectIconsAtlas and the textures beside it), cut out of the client by platform/tools/clientmarkers.py; a marker not imported is drawn as a plain grey dot.
- Whose it is
- Blizzard Entertainment's artwork, shown here by a fan site.
- Imported
| Measure | Value |
|---|---|
| Icons | 9,853 |
| Map markers | 35 of 35 |
Blizzard – the game's own API present
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.
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.
34 realms fetched from Blizzard's own realm index, and Blizzard's record of 3 characters -- profile, equipment, stats, specialisation -- with 66 pictures copied onto this hub, so no page links to Blizzard's servers. Held for at most 30 days and then re-fetched, which is what the Battle.net API terms require of anyone storing their data.
- 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 while its player keeps uploading -- at most every thirty minutes, less often when many characters share the hourly quota -- 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.
- Imported
| Measure | Value |
|---|---|
| Realms held | 34 |
| Namespace | dynamic-classic-eu |
| Retention limit | 30 days |
| Characters held | 3 |
| Pictures held | 66 (0.9 MiB, served from this hub) |
Blizzard – the 3D figures, from the game client's files present
The figure is drawn by this hub from the game client's own files, wearing what Blizzard's record, the addon's snapshot or this list says.
The 3D figure on a character sheet and on a best-in-slot list: the race's model, dressed in the items, the face, the skin and the hair the record names, standing as the game's character frame shows it. The 3D model on an NPC's page, and the small picture of it a link to the NPC shows when the pointer rests on it: the creature the game draws the NPC as, in its own skins, or -- for an NPC on a playable race's body -- that race dressed and groomed as the game's tables say the NPC is.
4,145 figures held, each drawn here from the game client's own files and served from this hub. A figure drawn from a character's Blizzard record is deleted with that record, at 30 days at the latest.
- Where it came from
- Drawn by this hub from the World of Warcraft client's own model, texture and table files (build 5.5.4), which it reads through wago.tools by file number. A character's figure is drawn from one record at a time: Blizzard's record of what it looks like (the Battle.net API's /appearance), or the PandaQuest addon's own snapshot -- the race, the sex, the items and the barber's choices the addon read in a barber's chair, the face and hair being the game's first choices until it has. A best-in-slot figure wears the list's items. An NPC's is drawn from the creature display Wowhead's page of the NPC names (the number the game draws it by), through the client's CreatureDisplayInfo, CreatureModelData and, for a humanoid, CreatureDisplayInfoExtra, CreatureDisplayInfoOption and NPCModelItemSlotDisplayInfo tables, and is built the first time a page here shows the NPC. The figure is kept on this hub and served from it, and a reader's browser contacts nobody else for it.
- Whose it is
- Blizzard Entertainment's artwork, shown here by a fan site. The drawing code is this site's own; its rules for which item covers which part of the body follow the MIT-licensed wow.export and WoW Model Viewer.
| Measure | Value |
|---|---|
| Figures held | 4,145 (833.6 MiB, served from this hub) |
| Client build | 5.5.4.70032 |
Wowhead – money, experience, item details, sell prices and the database's gaps present
Read from Wowhead in the background and kept: a quest's money and experience, an item's details and sell price, an NPC's or object's details -- and, only where the quest database has none, a quest's reward items, objective, givers and text. Until the answer arrives the page says what is happening rather than showing zero.
The money a quest pays, which no other source this hub can reach has at all, and the experience beside it. From the same page, and only where the quest database has nothing: the quest's reward items, its objective line and who starts and ends it, Wowhead's note that Blizzard marked a quest obsolete, the quest giver's text and the places Wowhead's map of the quest marks. An item's details -- quality, item level, binding, slot, stats, sockets, set, requirements, effects -- and its vendor sell price, read off the item's Wowhead tooltip. An NPC's or an object's level, type, reaction, faction and health, where it stands, what it sells and for how much, what it drops or contains and how often, and the number of the creature display an NPC is drawn by (the figure itself is drawn here, from the game's files). No picture comes from Wowhead, and nothing else on this site does either.
10,504 quests carry money or experience read from Wowhead. Every other quest says what is happening to those two fields. Nothing is waiting this minute: a quest is queued when its page is opened here, when a player runs it, and – up to 4,000 a day, behind both of those – when it still has no money figure.
- 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, and the tooltip or page of each item, NPC and object a page here shows: one at a time, at most one request every few seconds and a fixed number a day for all of them together, 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.
- Imported
| Measure | Value |
|---|---|
| Quests with money or experience | 10,504 |
| Quests answered by Wowhead | 11,382 |
| Quests waiting | 0 |
| Quests with an experience figure from any source | 10,508 |
| Items with details and sell price from Wowhead | 29,780 |
| NPCs with details from Wowhead | 14,010 |
| Objects with details from Wowhead | 950 |
| Items, NPCs and objects waiting | 0 |
Moderators – corrections to the quest database no corrections yet
Corrected on this site by a moderator: the import says otherwise. Every correction is in the changelog, which says what changed and never who changed it.
Corrections a moderator or an admin of this site made by hand to a quest, an NPC, an object or an item -- a name, a level, the objective text, who starts or ends a quest, where an NPC stands -- and what they added that no import has, or took off because it is not in the game.
Nothing on this site has been corrected this way yet: every quest, NPC, object and item is as its import wrote it.
- Where it came from
- Typed in on this site by a moderator or an admin. Kept apart from the imports, so the next Questie import does not undo them, and sent to the addon with its next update.
- Whose it is
- Facts about Blizzard's game, recorded by this site's moderators.
Players' suggestions – corrections a moderator approved no approved suggestions yet
Suggested by a player and approved by a moderator: the import says otherwise. The changelog lists it, without the player's name.
Corrections, additions and removals a signed-in player suggested from a quest's page and a moderator approved and applied.
Nothing on this site has been corrected this way yet: every quest, NPC, object and item is as its import wrote it.
- Where it came from
- Sent by a player from the suggestion form, and read and approved by a moderator before anything changed. The change itself carries no name; the player's own words are not shown.
- Whose it is
- Facts about Blizzard's game, suggested by a player and checked by a moderator.
Players – what they did present
Uploaded by players running the addon. Self-reported: nobody verifies it, and it is only as complete as the people who chose to upload.
Everything about what actually happened: sessions, quest runs and their timings, coordinates, kills, deaths and turn-ins, and the flights taken from a flight master with how long each took and what it cost.
49,279 events from 8 character records, uploaded from 6 signed-in computers. Self-reported, and only from the people who chose to install the addon. A record is one Name-Realm on one computer, so a character synced from two computers is two of them, and a character its owner has hidden is still one -- this page counts what the hub holds, which is not the same question as the front page's “how many characters can you see”.
- 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
| Measure | Value |
|---|---|
| Telemetry events | 49,279 |
| Quest runs | 1,528 |
| Play sessions | 173 |
| Character records held | 8 |
| Uploading computers | 6 |
| Registered accounts | 6 |
PandaQuest – our own analysis present
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.
Routes, hotspots, median times, objective order, leaderboard positions, flight times – everything this hub works out rather than receives.
1,142 quest guides published from 1,528 recorded runs. 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. Every figure is an observation with its sample size, never a fact about the quest.
- 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'.
- Imported
- 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
| Measure | Value |
|---|---|
| Published guides | 1,142 |
| Runs behind them | 1,528 |
| Death map threshold | 5 characters, 2 people |
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.
A 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
PandaBase 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.
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 legal notice says who to write to.