What a World of Warcraft build number means
A World of Warcraft build number like 1.15.9.69722 has two parts: a version (1.15.9) and a build id (69722). The version is the patch label; the build id is the specific client Blizzard compiled and shipped. Two builds can share a version and differ only in build id, so ForeverDiff records the full build number plus the exact config hashes Blizzard's patch server reports, and every value on the site traces to one exact build. On its pages the site names a build by the day it was first seen, and the full version sits in each page's provenance line.
- Version (1.15.9): the patch label, shared across many builds.
- Build id (69722): the specific client compile, unique to that build.
- We store both, plus the BuildConfig and CDNConfig hashes, so a value is never ambiguous about which client it came from.
- Pages name a build by the day it was first seen; the full version is in the provenance line, the build page and its URL.
The version and the build id
Read left to right, 1.15.9.69722 is a version (1.15.9) followed by a build id (69722). The version is the human-facing patch label. The build id is an incrementing number Blizzard assigns to each client it compiles, so it climbs even when the version does not change.
Why the build id matters
The same patch can ship as several builds. The Classic Era builds 1.15.9.69722 and 1.15.9.70003 share version 1.15.9 and differ only in build id. If we recorded only the version, a value could belong to either. Recording the full build number, and the config hashes below, removes that ambiguity.
How this site names a build
Nobody remembers a build number, so the rest of the site names each build by the day it was first pulled here from Blizzard's CDN: "the Sep 29, 2026 build". That is not a release date; Blizzard publishes none for these clients. When two builds of one client were first seen the same day, each also carries its short build id: the Forever builds 1.60.1.69893 and 1.60.1.69913 were both first seen on Sep 17, 2026, so they read "Sep 17, 2026 (69893)" and "Sep 17, 2026 (69913)". The full version is in every page's provenance line, on the build page and in its URL. See how builds are named in the methodology.
How we read it, and what we store
We poll Blizzard's public patch server, which lists, for each product, the current build with its BuildConfig and CDNConfig hashes. We store those hashes verbatim in each build's dataset record, along with the pinned version of the community column definitions we parsed with. That record, re-hashed against the committed data at build time, is what makes every value on the site checkable. See the methodology and any build page for the exact fields.
Frequently asked
Is 1.15.9.69722 the same as patch 1.15.9?
It is one specific build of patch 1.15.9. The patch (the version) can ship as multiple builds, each with its own build id. ForeverDiff records the full build number for every build, names it on its pages by the day it was first seen, and shows the full version in each page's provenance line and on the build page.
Where does ForeverDiff get the build number?
From Blizzard's own public patch server, which advertises each product's current build and its config hashes. We record those hashes so the data traces back to the exact client.