Sources
How we know what we know
Every fact on Bind on Forever carries where it came from, which game build it was checked against, and how sure we are. This page explains the sources and the order they rank in.
The order we trust sources in
When two sources disagree, the higher one wins and the page says so. A lower source never overwrites a higher one.
| Rank | Source | How the page shows it |
|---|---|---|
| 1 | The game itself. The WoW Forever client's data tables, the server's own values from our client's hotfix cache, and what we record playing the game. | "Game files" or "Server data" with the build number and date; "Seen in game" for our own play. |
| 2 | Blizzard. Patch notes, development notes, known issues, hotfix lists and developer interviews. | A link to the post, and each line marked as matching the files or not. |
| 3 | Other databases. QuestieDB for quest givers, objectives and spawn points; Wowhead, Icy Veins and Warcraft Wiki for lookups. | Credited by name, and marked "not yet checked in game" until our own play confirms it. |
| 4 | Leads. Creators' videos, Reddit posts and news reports. | Quoted with the speaker and a timestamp, never stated as fact until the files or Blizzard agree. |
The game files, build by build
We read the client's data tables for every WoW Forever build since Sep 16, 28 builds so far, 10 of them on the live game, through wago.tools. Each build is compared field by field with the one before it and with Classic Era 1.15.9.70576. That's how the site can say what changed, when, and whether Blizzard's notes mentioned it: see every build's changes and Blizzard's notes, checked.
The newest build on the site is 1.60.1.70862, from Nov 7, 2026. Pages built from it say so in their source box.
Server data and encrypted items
Blizzard can change values on its servers without a new build, and new WoW Forever items are encrypted in the client until they're seen in game. Our own game client keeps the values the server sends. We read them after each play session, so a page can show the server's current number where it differs from the files. Those pages say "Server data".
Our own play
We play WoW Forever with a recording addon of our own that notes what we loot, what vendors sell and for how much, quest givers and turn-ins, experience, creature levels and our own deaths. It sends nothing anywhere; we import the files by hand. Rows from our play are marked on item and quest pages. Combat logs help us list what creatures cast, but we only publish counts: never other players' names.
Blizzard's posts
Every Blizzard post about WoW Forever is archived, including later edits, and the living documents (development notes, known issues) are kept version by version. Articles quote them with a link and the date, and check each claim against the files.
Other sites we credit
- QuestieDB: Classic quest data on Forever's map, plus its own Forever additions. We publish the facts in our own pages and credit it where its data is used.
- wago.tools: the client tables of each build.
- Wowhead and Icy Veins: looked up and linked, never copied. One exception, credited on the map: Zephras Isle's ore and herb spots, read once from Wowhead's Forever map because no other source has them.
What we don't publish
- Other players' names, from combat logs or anywhere else.
- Whole transcripts or articles from other people: we quote a line and link the source.
- Raid spoilers without a warning: boss rosters and newly readable items sit behind a spoiler fold.
- Rumours as facts. A claim we can't check says who made it.
Mistakes
When we get something wrong, we fix it on the page, add the date, and say what changed. How to tell us, and the recent fixes: corrections. Who writes the site: about Bind on Forever.