Where the catalog data comes from
BISPath builds every D4 page from datamined game files plus a few community references. The structural data — items, aspects, affixes, skills, paragon — comes from d4data, a community-maintained extract of Blizzard's client files, and the localized text comes from the game's own English and Korean string dumps. Three references fill specific gaps: Inven (Korea) supplies pre-rolled affix detail for the items it has indexed and the cleaned-up skill tag labels like Core, Basic, and Defensive; Wowhead supplies item icons and tooltip metadata — inherent affixes, required level, class restrictions — for the roughly 130 newest Lord of Hatred uniques Inven has not reached yet; and Maxroll's planner export supplies the affix value-range formulas that turn an item-power number into a concrete stat range. When a reference disagrees with the client files, the client files win.
How the planner uses the catalog
Every unique, aspect, affix, skill node, and paragon glyph in the catalog is pickable inside the build planner at /d4/[class]/build. The planner combines skill tree allocation, paragon board attachment, gear slot configuration, mercenary selection, and stat priority into one shareable URL. When you save a build, BISPath encodes the entire planner state — class, level, skill ranks, paragon paths, equipped uniques, aspects, and affixes — into a short share code. Open the link from anywhere and the planner restores exactly what you saved. Builds you create while signed in show up in the My Builds drawer; share-code links are read-only and never require sign-in to view.
Catalog scope and freshness
The catalog covers 736 unique items, 585 legendary aspects, 2,780 affixes across every tier (magic, rare, legendary, mythic, runeword) and 135 tempering affixes. All live classes ship with their complete skill tree and paragon board set, including glyph radius math and gate attachment logic. Catalog pages render the full set on first load with client-side filtering by class, slot, search term, and (where applicable) damage type. Refresh runs on demand whenever the d4data export updates; the build stamp at the top of this page reflects what BISPath is serving right now. The Blizzard Game Content Usage Policy attribution sits in the footer of every D4 page, since the underlying game text and item names remain Blizzard's intellectual property.
Frequently Asked Questions
Does the catalog reflect the seasonal realm or eternal?
Both. The live patch is shared between season and eternal, and BISPath's catalog tracks the live patch directly via d4data. Class balance numbers, skill effects, affix rolls, and unique drops are identical across the two realms unless Blizzard ships a realm-specific change — which is rare. Build share codes don't encode which realm a build is for, so you can copy a seasonal build into eternal without modification.
Why doesn't BISPath rank items with tier letters (S / A / B)?
Because tier lists go stale within days of a patch and steer players toward herd builds. The catalog tells you what an item does; the planner shows you what your build does with that item. For aggregated community choices the better starting points remain Maxroll's tierlist and Mobalytics' build tracker. BISPath sits in the gap between those tier lists and the in-game tooltip: a place to try the build before committing to it.
When does the catalog data refresh after a patch?
Whenever the datamined export catches up — usually within a day or two of patch release. The version stamp at the top of this page shows the build currently loaded. If the stamp is behind the live patch, either the upstream export or BISPath's own extraction has not caught up yet, and class-balance fields may be slightly behind. Catalog text (item names, descriptions) updates fastest; affix rolls and skill formulas typically follow within the same extraction pass.