About the data

Where it comes from

• The game's own data – the quests, the names of the NPCs, objects and items they mention, the shape of the world map and the level range of each zone, the flight points and the professions. It is the same on every realm and nobody's play changes it, and it is loaded into this site by its operator.
• The best-in-slot lists – the items, levels, stats and bosses on Best in slot are read once, by a tool, and kept in this site's source. The order of each list is a weighted sum of an item's stats, with the stat priorities written down from published class guides; each page names the guides it used and the day they were read. It is ranked, not simulated, and it has no drop chances, vendors or prices because the data has none.
• Players, and PandaBase's own analysis – the sessions, timings, deaths and gear that people chose to upload with the addon and the companion, and the routes and medians this site works out from them. Nothing is uploaded unless the player opted in, and everybody can export or erase their own.

Every source by name, with its licence, its version and what it covers, is on Sources.

How it stays current

Nothing here is on a timer you cannot see. The quest and item data is loaded by the operator when a new release is built, so it is as old as its import date. The zone maps and the figures the quest data lacks are fetched in the background, a little at a time, and each answer is kept rather than asked for again. What players did arrives when the companion uploads it, and the guides are worked out again after uploads.

The guides were last worked out 15 h ago, from 93 quest guides. Each source's version and import date is on Sources.

How to read a number

What a quest is – its objectives, rewards and chain – is the same on every realm. What players did is self-reported and only as complete as the people who uploaded, and everything this site works out from it is an observation with the number of runs behind it, not a fact about the game.

A thin badge beside a run count means too few runs to call a route yet; a plain count is a guide you can lean on, and the more runs, the better it gets. A figure that cannot be worked out is shown as missing, never as zero.

Spotted a mistake?

The database is a community's best copy of a game that keeps changing, so it has mistakes: a quest in the wrong zone, a missing note, a wrong level. If you find one, tell us.

Tell us what to fix See every source

You can also write to ba@zroot.it.

Ask your AI assistant – PandaBase speaks MCP

Everything on this site is also there for AI assistants that support the Model Context Protocol (for example Claude Desktop or Claude Code). Connect one once, and ask it in plain words: who gives a quest and where they stand, where an NPC spawns and what it drops, the fastest flight between two points, the best-in-slot list for your spec – and get this site’s answer, with coordinates and links back to its pages.

1. Sign in with Battle.net and open Developer.
2. Make a key. It is free, read only and lives 182 days.
3. Paste it into your MCP client’s settings:

{
  "mcpServers": {
    "pandaquest": {
      "url": "https://pd.zroot.it/mcp",
      "headers": { "Authorization": "Bearer pqk_YOUR_KEY" }
    }
  }
}

12 read-only tools: search, get_quest, get_npc, get_object, get_item, get_zone, list_realms, get_character, list_my_characters, get_bis, get_flight_route, get_changelog. Up to 60 requests a minute and 5,000 a day per key.

Connect your assistant