Mage at character selection
In the original v0.91.0 (0d319264) selector, Mage starts with Fireball and displays 215 health. The selected race was Undead, equipment was empty and the talent counter showed 0/51. This is a UI observation, not a combat benchmark.
The selector presents the class around area damage with limited defenses. Treat that as the game’s description of its intended style, not proof of comparative strength. See the full nine-class starting reference for context.
Character-selection UI, v0.91.0 (0d319264), inspected October 15, 2026. All nine class tiles, displayed health, starting spells and selected races were read directly. No full combat test was completed.
What players reported
One launch-thread player calls Mage strong. Elsewhere in the same discussion, a player reports needing to kite on Mage and Warlock to stay alive. These are first-person impressions, but neither supplies a version or a controlled comparison.
The report comes from the original launch discussion ↗. It is not controlled playtesting and does not establish a current best build. Our tier list evidence page keeps all three class reports in the same context.
Original selector observed at v0.91.0 (0d319264); community reports do not specify their builds. We do not have a tested Mage upgrade order, damage benchmark or optimal talent allocation.
The useful question for your next run
Can you keep enough space to survive while maintaining useful damage against both waves and bosses?
Use the prompts below to investigate your own setup. They are editorial guidance for gathering evidence, not verified properties of the class.
- Note whether a death follows a positioning mistake or a lack of damage. Those are different problems and may call for different upgrade choices.
- When your current build offers control or movement options, record whether they actually create safer space. Do not count an ability as helpful merely because its tooltip sounds defensive.
- Track boss completion alongside wave survival. A comfortable wave-clearing run is not proof of strong single-target performance.
How to approach a Mage build
Treat mobility, control and damage as questions to test against the cards actually offered in your version. If you repeatedly lose while surrounded, compare one available space-making option with your usual damage upgrade. This is an experiment, not a published best-in-slot build.
Read every offered card in your current client. Record the permanent items and Talent XP investment you started with, since the progression described at launch can affect later attempts. If the client changes, re-check the build instead of assuming an older sequence still applies.
Compare a result, not a reputation
Keep map, mode and starting progression similar across attempts. Save both successful and failed runs, and record the choices that differ. Use the run notebook to capture survival, boss outcomes and the cause of a loss. A result is most useful when another player can understand its conditions.
Neither a positive community comment nor the class’s role in World of Warcraft is enough to determine its ranking in Azeroth Survivors. The alpha’s current implementation matters.
Source & version scope
Primary source for browser play, progression and the community reports cited here. Community comments do not identify their build numbers. Original selector observed separately at v0.91.0 (0d319264).
Community reconstruction README ↗ — used only to identify the separate project, not to rank the original.