The people behind the pages

A companion for the climb.

An independent field guide to Spires of Azeroth, built for the moment between a difficult run and a better idea.

Independent, and clearly so

This website is an unofficial fan guide. We are not Chris Lucas, TheWoWDB or Blizzard Entertainment, and we do not operate the playable game. The game is developed by Chris Lucas and TheWoWDB contributors.

Use TheWoWDB to play and the developer’s GitHub releases for downloads.

The source behind a number

Card effects, class data, talents, equipment and encounter records come from the open-source game repository. The data pages identify the source snapshot so a displayed number can be traced to a commit.

Recorded version
1.0.3
Source commit
68932e1
Upstream copyright
© 2026 Chris Lucas & TheWoWDB Contributors
Data and code license
MIT License and upstream notice

The playable game can change before this guide refreshes. Check the card in your current client when a result differs. Read the data update log →

Advice, data and simulation

Database entries reproduce source data. Class builds are editorial suggestions based on card interactions; they are not claims that a deck has been proven optimal. The class comparison page separates measured simulator results from practical reading advice.

Simulation outcomes describe an automated policy, its settings and its seed sample. They are not a human-player win rate, a tournament ranking or a promise about your next run.

Respecting the original work

We link to the game rather than embedding or hosting a playable copy. We do not mirror the developer’s installers or the game’s Blizzard art, models and audio. Any game screenshots are identified as captures rather than original artwork.

World of Warcraft, Warcraft and Blizzard Entertainment are trademarks or registered trademarks of Blizzard Entertainment, Inc. All associated game artwork and audio remain the property of their respective owners. The upstream MIT license does not transfer ownership of third-party assets.

Corrections and game support

For a game bug, use the in-game report button or the developer’s issue tracker. For a guide correction, email [email protected] with the page URL, the current source version and the specific effect or statement that needs attention. Never include passwords, account tokens or private save data in a report.