Skip to content

Data files

Markdown
The game's classes, spells, talents, rings, amulets, stat caps, set bonuses and zones as JSON files on azreborn.com, free to use in your own tools: where they are, what they hold and what stays stable.

The game's content is public. Classes, spells, talents, rings, amulets, stat caps, set bonuses and zones are published as plain JSON files, so you can build a talent planner, a Discord bot, a spreadsheet or a fan site without asking us. Any web page may read them directly: the files are served with access-control-allow-origin: *.

Where they are

All files live under https://azreborn.com/data/v1/. Start with the index:

https://azreborn.com/data/v1/index.json

The index lists every file with the number of records, its size in bytes and the fields of each record, so a tool can read the layout from the index instead of from this page. It also carries a content value that changes whenever any file changes: keep it with your cache and fetch the rest only when it differs. Files are cached for an hour.

The files

FileWhat it holds
classes.jsonOne record per class: its id, key, colour, the race ids it can be played as, its starting health and damage modifiers, its first spell and the keys of its spells.
spells.jsonThe spells of every class: the 3.3.5a spell id, icon, school mask, base hit, cooldown and range.
talents.jsonEvery talent of the three trees of each class, with its place in the tree, its ranks, its text, the talent it requires and the group it is exclusive in (see "Talent builds").
jewelry.jsonRings and trinkets.
amulets.jsonAmulets, with their rarity, the classes they are offered to (an empty list means every class), their numbers at rank 1 and how they grow (see "Amulet numbers").
legends.jsonThe legendary amulet of every spell that has one, already resolved: one record per spell with the amulet's id, its title, the entry it comes from and its effects (see "Legendary amulets").
caps.jsonThe limits on a hero's stats (cooldown reduction, critical strike chance, damage reduction, the chance to cast again, haste buffs), each with the talents that raise it (see "Stat caps").
set_bonuses.jsonThe set bonuses, with the class (null for a bonus every class may wear), the tier, the number of pieces and the text. {v} and {v2} in the text stand for the strings in v and v2.
zones.jsonThe zones in the menu's order, with their difficulty factors and their bosses.
i18n/<locale>.jsonFor each language other than English, a map from an English string of the files above to its translation.

Reading the values

  • Texts and names are English. To show another language, look the English string up in i18n/<locale>.json (deDE, frFR, esES, ptBR, ruRU, itIT, plPL, trTR, jaJP, zhCN, koKR) and keep the English one when it is not there.
  • A class is named by its key from classes.json (mage, deathknight) in every other file.
  • A spell's hit, cooldown and range are its base values. The game raises them by the hero's level, cards, jewelry and stats, so a tool that wants the damage a hero deals has to apply those itself. school is the 3.3.5a school mask: 1 physical, 2 holy, 4 fire, 8 nature, 16 frost, 32 shadow, 64 arcane.
  • A talent's text holds {v}, which stands for value times the ranks taken. Where {v} is followed by % and value is below 1, the value is a share and the game shows it times 100 (0.03 is 3%). A value of 1 or more is already a percentage (Entrapment's 6 is 6%), except in Splitting Ice (1 is 100%) and Blood Frenzy (2 is 200%). Without a % the number is shown as it is.
  • icon is a file name on Wowhead's icon CDN: https://wow.zamimg.com/images/wow/icons/large/<icon in lower case>.jpg.
  • A field that does not apply is null, never missing.

Talent builds

A hero spends talent points in the three trees of its class. These are the rules the game applies to a build, so a planner can apply them too:

  • A tree's hub costs one point and opens the tree; no talent of it can be learned before. A class holds 52 points in all.
  • A row opens at five points for each row above it in the tree, the hub's point included: row 2 needs 10 points in the tree, row 6 needs 30. row counts from 0.
  • A talent with requires needs that talent (a key of the same tree) at its full ranks.
  • A talent's exclusive is null, pair or a group's name. Of the talents that share a value, one can hold ranks: pair is the two talents of that tree's pair, and a named group (stance, legion) spans the three trees of its class. The one-rank talents of row 6, the capstones, rule each other out within their tree whether exclusive names them or not.
  • A build string has a digit for each talent of a tree, in the order talents.json lists them, then a digit for the hub (1 open, 0 shut). The three trees are joined by -. The game reads a string as far as it goes and drops every rank these rules would not allow.

The Build Planner on the site, /planner/<class>, applies exactly these rules to this file and keeps the build in the address: ?b= is the build string alone, ?p= a whole build (talents, spells, jewelry, amulets, stats and notes of its four phases). It plans with classes.json, spells.json, jewelry.json, amulets.json, legends.json, set_bonuses.json, caps.json and talents.json, and reads the best runs from the leaderboards for its pick rates.

Legendary amulets

A legendary amulet belongs to one spell, so legends.json has one record per spell with one, instead of one per amulet entry. The game works out which amulet a spell gets, and the file hands you the result, so you never have to guess it from the spell's shape:

FieldMeaning
keyThe amulet's id in the game, always legendary:<spell key> (legendary:mind_sear). This is the one stable, unique key.
spell, classThe spell (its key in spells.json) and the class whose spell it is.
nameThe title as the game shows it: <head>: <spell name> (Amulet of the Inferno: Mind Sear). Some of the game's own entries carry no spell name and are the head alone.
headThe name without the spell's. Many spells share one head (The Eternal Talisman belongs to more than forty spells), so never use it as a key. Heads are English only for now: i18n/<locale>.json does not carry them, though it does carry the spell names.
iconThe amulet's icon, as everywhere else.
templateThe entry in the game's data the amulet comes from: either the spell's own (cleave), or a generic one (generic_ground).
formnull when the spell has an entry of its own. Otherwise the shape that picked the generic entry: bolt, missiles, nova, ground, chain, melee, dot, execute, cone, lasting, totem, instant, immune or summon.

How a spell gets its amulet:

  • An entry written for the spell itself always wins. A spell without one takes the generic entry of its shape, and every shape has exactly one generic entry (the template).
  • A strike that reaches further than 8 yards is a bolt, a strike at arm's length is melee. A heal over time, an all-damage buff, a haste buff and a thorns buff are lasting; a shield, a healing sphere and a heal that lands at once are instant; an immunity is immune. Totems and orbiting spells are totem, summoning and commanding spells are summon, and missiles, nova, ground, chain, dot, execute and cone are what their names say.
  • A spell that is not in legends.json has no legendary amulet. That is the case for the spells the game takes out on purpose (legendary: false in spells.json: Healing Wave, Lightning Shield, Demonic Knowledge) and for passive spells (Call of Flame), which say legendary: true there and still have none. Trust legends.json, not that flag.
  • There is no class restriction on a legendary itself. A hero is offered the amulet of a spell they know, so in practice it drops for the class that has the spell. Two spells are dealt to one faction only (Bloodlust to the Horde, Heroism to the Alliance), and some spells (the monk's stance spells, for one) reach a hero only after a given talent has been taken; their amulets are listed all the same.
  • The fixed amulets of amulets.json are separate. Their classes list names the classes they are offered to.

New spells and amulets appear here by themselves: the files are written from the same data the game runs on, so a spell added in a game update shows up with its amulet once the site is updated. The file lists amulets whether or not you own them, so you can plan a build before you ever find one. What the amulets do, and how that grows with their rank, is in the next section.

Amulet numbers

amulets.json and legends.json carry what an amulet does at rank 1. An empower card in a run raises the rank by one, and the numbers grow toward three times their rank 1 value by one rule, with the amulet's own growth:

multiplier = 3 − 2 × (1 − growth / 2) ^ (rank − 1)

Rank 1 is 1×, and a growth of 0.2 gives 1.2× at rank 2. legends.json carries growth too; the shaman's pieces, which grow another way, have it null and a fixed value instead.

  • Fixed amulets (amulets.json). effects is a list of { "stat", "value" }. A value is a share (0.15 is 15%), except for regen and kill_heal (health), and lives and targets (whole numbers). At rank r each value is value × multiplier; targets grows in whole steps instead, rounded down. special is null or what the amulet does besides, written as the game's data writes it: { "ignite": 0.8 } is a share that grows with the same multiplier, "cheat_death" has no number. world (null for every world) and needs ("heal": offered only to a hero who knows a heal) say when an amulet drops.
  • Legendary amulets (legends.json). effects is a list of what the amulet does to its spell at rank 1, each written as the game's data writes it: a name with its numbers ({ "damage": 0.5 }, { "burn": { "secs": 6, "share": 0.8 } }) or a name alone ("reset"). Keys inside an object are in alphabetical order. At rank r, the shares and strengths (damage, area, power, duration, a share) are multiplied by the multiplier. Chances (again, a chance) are multiplied too but stop at 1, and a cooldown cut stops at 0.5. Seconds, radii and counts (secs, radius, n, pct) stay as they are, and targets grows in whole steps. A piece with a fixed value grows only in damage and area, linearly: the multiplier is (fixed + 0.05 × min(rank − 1, 10)) / fixed, and it is not offered past rank 11.

Stat caps

caps.json lists the limits a hero's stats run into: the same numbers the game applies and the addon API tells (AZS_GetStatCaps). Every record has the stat's key as the addon API names it (cdr, crit, red, echo, haste), the cap in whole percent, a name and a text that says what it limits. raised_by lists the talents that lift the cap, each with its class, talent key, name and the percent points it adds when taken in full (the warrior's Titan lifts damage reduction). The list is empty for a cap nothing raises.

These are the caps of a hero's stats. They are not the limits of a single spell (its targets), of the dash upgrades or of the jewelry sets.

What stays stable

The files follow the live game, and after a site update they may already hold content of the next game update. Within v1 we only add fields and files; we never rename or remove one. A change that would break a tool moves the files to /data/v2/ and raises schema in the index, and v1 stays up for a while.

Example

Every spell of the mage:

const base = 'https://azreborn.com/data/v1/'
const spells = await (await fetch(base + 'spells.json')).json()
console.log(spells.filter(spell => spell.class === 'mage').map(spell => spell.name))

What is not in the files

Spell descriptions, armor and weapon pieces, enemies, cosmetics, game modes and everything about players. The leaderboards and the armory have their own endpoints.