Warrior · original-game field notes

The Warrior field guide.

An early strength report, with a closer look at what would make the comparison fair.

Warrior at character selection

In the original v0.91.0 (0d319264) selector, Warrior starts with Cleave and displays 230 health. The selected race was Human, 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 close-range cleaving attacks. 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.

Direct observation
Aethus’s original game ↗

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

A reply in the original launch thread describes Warrior as strong, but the statement is second-hand: the commenter is relaying a friend’s opinion. There is no version, build, equipment list or recorded run attached.

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.

Build status: unverified

Original selector observed at v0.91.0 (0d319264); community reports do not specify their builds. We do not have a tested Warrior upgrade order, damage benchmark or optimal talent allocation.

The useful question for your next run

Does a repeatable opening survive pressure without relying on accumulated permanent gear?

Use the prompts below to investigate your own setup. They are editorial guidance for gathering evidence, not verified properties of the class.

  • Keep permanent equipment and Talent XP comparable between attempts. A geared Warrior run does not establish how the class performs from a fresh start.
  • Record when enemies first force you to retreat, and which upgrade you chose immediately before that point. This is more useful than an unqualified claim that the class feels strong.
  • Compare boss outcomes separately from time survived. A run that stays alive longer can still struggle to finish a boss.

How to approach a Warrior build

Use the upgrade descriptions in your current game as the starting point. If you are losing to contact damage, test an available defensive option against your usual damage pick. Keep the other conditions as similar as possible; do not assume retail or Classic WoW talent rules apply.

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

Follow the evidence
Original launch announcement & player discussion ↗

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.