Guide · updated for build v0.90.0

Azeroth Survivors Guide: Best Classes, Builds & How to Play

What is Azeroth Survivors?

Azeroth Survivors is a fan-made roguelike by Aethus, hosted at wow.aethus.pl. It takes the survivors-like formula — one hero, endless waves, automatic attacks, an upgrade choice every level — and sets it inside a from-scratch reimplementation of the World of Warcraft 1.12.1 client. You are not playing a WoW addon, a private server or a streamed video: a real 3D client is running in your browser tab.

Technically it is the benilla WoW client engine, written from scratch in Rust with the Bevy engine, compiled to WebAssembly and served as plain static files. That architecture explains almost everything about how the game feels to use:

• No game server and no account. There is nothing to sign into, and nobody is hosting your run. The world data is downloaded and the simulation happens locally.
• WebGPU is mandatory, and that is the one real gate. The 3D world is drawn with the modern graphics API, so an older browser cannot start the client at all.
• The first load is heavy, the second is not. A cold start streams roughly 140 MB of world data across about a thousand requests; your browser caches it, so returning is fast.
• Runs are long-ish and timed. Bosses arrive on a clock rather than at the end of a wave counter.

Start here

How to play Azeroth Survivors: the full control scheme

This is the section the game itself never gives you. The client draws its UI onto a canvas, so there is no tooltip anywhere on its page explaining what the keys do — the whole scheme is one line of text on the run screen and a controls file in a community repository.

The single most important thing to understand: your abilities cast themselves. You never press a key to attack. Every input you have is about where you stand, which upgrade you take, and when you spend your movement spell.

The movement spells are worth knowing about before you pick, because they are the clearest difference between classes in practice: Blink, Charge, Sprint, Dash, Fade, Ghost Wolf, Aspect of the Cheetah, Blessing of Freedom and Howl of Terror — one per class, all on F.

Play it now in your browser

Your first run, step by step

The character screen is the only menu you have to learn, and it does all the work: race, gender and class on the left, your hero and equipment in the middle, the zone chain on the right, and the button that starts everything at the bottom.

1. Pick a race, then a gender, then a class. There are eight races and both genders, and each race can only be certain classes — the same restriction the game it is modelled on uses. Races bring their racial traits with them; the game prints them in the chat log when the run starts (playing a Human, for example, gives Perception, The Human Spirit and Diplomacy).
2. Choose a zone. Only Elwynn Forest is open on a fresh save; every zone you complete unlocks the next one in the chain, and the panel tells you exactly which boss opens which gate. Each entry also lists the creatures that live there and the boss schedule you are signing up for.
3. Set your run options, then press Enter. The run screen shows a difficulty selector (Normal by default), which class and zone you took, and a reminder that the zone's final boss is waiting at a fixed time.
4. Move to begin. The world loads, the run clock is already displayed at the top of the screen, and the first wave spawns around you. Your abilities start firing on their own.
5. Take a card at every level, then keep moving. Kills, gold and caches tick up in the top-right; the next boss is always counting down in the middle. When the finale boss dies, the zone is cleared and the next one in the chain unlocks.

Most-asked question

What is the best class in Azeroth Survivors?

For a first run, Paladin. It starts with the largest health pool in the game and a self-heal, and it gets one free death. Hunter is the other forgiving pick: 240 health and an opening attack that kills from range, which lets you learn the movement without standing inside the swarm.

Beyond that, “best” depends on how you play, because each class kit follows the class it is named after: the Warrior wants to be surrounded, the Mage wants to never be touched, the Warlock needs fights to last long enough for its damage-over-time to matter. The game's own picker tells you which is which in one line each.

Starting health and opening spell, read from the class picker in build v0.90.0.

Class	HP	Starts with	The game's own description
Paladin	245	Consecration	Holy ground and righteous hammers. Heals himself, shrugs off death once in a while.
Hunter	240	Auto Shot	Death from range. Arrows, traps and volleys, as long as you keep your distance.
Warrior	230	Cleave	Unstoppable in the thick of it. Huge health, cleaving swings, and every kill feeds the fury.
Mage	215	Fireball	The glass cannon. The biggest area damage in Azeroth, and nothing to hide behind.
Druid	205	Wrath	Moon, storm and growth. Roots, hurricanes and the steadiest self-healing.
Shaman	195	Lightning Bolt	Storms that jump from foe to foe, and totems that fight beside you.
Rogue	190	Sinister Strike	Fast, fragile and lethal. The quickest hero, with crits that delete elites.
Priest	170	Smite	Light and Shadow. Shields and heals keep you alive while pain spreads through the horde.
Warlock	165	Shadow Bolt	Curses and fire. Damage over time stacks up on everything that chases you.

Grouped by how they play

• Front-line bruisers — Warrior, Paladin, Rogue. Warrior and Paladin trade mobility for the two biggest health pools and attacks that hit everything in front of them; the Rogue is the opposite bet, the fastest hero alive with the fourth-lowest health.
• Ranged casters — Mage, Warlock, Priest, Shaman. All four kill from a distance and all four die quickly when something reaches them. Mage has the biggest area damage and 215 health; Warlock has the lowest health in the game at 165 and needs the fight to last; Priest survives on shields rather than health; Shaman spreads damage between targets with chain lightning and totems.
• Hybrids — Hunter, Druid. Comfortable at range and survivable when it goes wrong. Hunter's 240 health with a ranged opener is the easiest way to learn a new zone; Druid's self-healing is the steadiest in the game.

Is there a tier list?

Not an honest one, and you should be suspicious of any page that gives you an S/A/B ranking without saying how it was measured. Azeroth Survivors is a randomised roguelike, the difficulty multiplier has been rebalanced more than once during the game's first weeks, and a class's power depends heavily on which cards you are offered. What can be measured is the starting position the game hands you, and that is the table above: health pool and opening spell.

On that measure — survivability in the first few minutes with default cards — the ranking is Paladin, Hunter, Warrior, Mage and Druid at the top, Shaman and Rogue in the middle, and Priest and Warlock at the bottom until you have learned to keep them out of contact.

Builds and level-up cards

Every level offers three cards. They are tinted the way Warcraft tints loot — the colour tells you the rarity — and each card states the exact change it will make, in the form Damage 20 » 26 or Targets 2 » 3. There is no hidden maths to reverse-engineer: the card tells you what it does, which means your build is really a series of honest choices about what your run needs next.

Three rules cover most decisions:

1. Early, take damage and targets over everything. Waves scale with time, not with your level, so the first five minutes are a race to kill faster than the spawner. A card that raises targets turns a single-target opener into a crowd-clearer, which is usually worth more than a small raw damage increase at that point.
2. Mid-run, fix the weakness your class started with. Warlock and Priest need survivability earlier than their health pool suggests; a Warrior with 230 health can afford to keep stacking offence longer than a Rogue with 190.
3. Before a boss timer, spend on defence. The clock is displayed on screen and the boss arrives whether you are ready or not — a mobility or healing card taken at 2:40 is worth more than a damage card you never get to use.

Rerolls exist for the moment all three cards are useless to you. Rerolling early is usually a mistake: a mediocre card now beats a wasted level while a wave is on top of you.

Levels also grant things you never choose, and the chat log states them exactly. A Warrior reaching level 2 mid-run reads “You have gained +3% damage, +9 maximum health and +0.08 health per second” immediately followed by “You have learned a new ability: Battle Shout (Rank 1)”. So a run grows on two axes at once — the stats you pick and the abilities the game hands you — and the second one is why a class can feel completely different at level 8 than it did in the first minute.

Progression

All nine zones, and the order they unlock

Azeroth Survivors does not give you a zone list to browse; it gives you a ladder. The picker shows your open zones and locks the rest behind the final boss of the zone before, so the progression is a chain you can read straight off the panel:

Start with Elwynn Forest

Elwynn Forest is both the first zone and the tutorial you will actually use. Its own panel describes it as kobolds pouring out of Jasperlode Mine while gnolls cross the river and the Defias Brotherhood marches on the farms, and it names the creatures you will meet by name — Kobold Vermin, Young Wolf, Murloc Streamrunner, Kobold Geomancer, Defias Thug, Riverpaw Brute, Prowler, Defias Rogue, Wizard and the Defias Enforcer.

Its boss schedule is the template for the whole game:

So a cleared zone is roughly a sixteen-minute commitment, with a boss every three minutes and a real difficulty step at each one. If you can reach VanCleef, you can read the zone.

Later zones are not just harder stat-wise: each one brings its own creatures and its own named bosses from the area it is modelled on, so the challenge is partly that you no longer know what is about to walk out of the trees.

Playing Azeroth Survivors on mobile or Android

It works, with honest caveats. The client ships touch controls, and the first tap requests fullscreen and a landscape lock, so it is clearly built with phones in mind. On Android it also adapts itself: the client disables its shader warm-up pass and drops to a lighter material shader, because a full pipeline warm pass has crashed some Adreno GPU drivers.

Players report it running on Android Chrome, Android Firefox and on iPad, and one thread on r/WoWPrivateServers is entirely about running it under Winlator on a phone and moving save states between PC and mobile. The caveats are real though: it needs a WebGPU-capable browser (so on iOS that means a recent iOS Safari), the interface is designed around a keyboard, and some mobile devices reportedly go black on load.

Our recommendation: play on a desktop or laptop. Use your phone for a quick run only if your browser supports WebGPU and you are comfortable with touch controls.

System requirements and browser support

There is no CPU or RAM specification worth quoting, because the wall everyone hits first is software, not hardware: the client needs WebGPU. It draws a 3D world, and it will refuse to start rather than fall back to something slower.

Two more practical numbers, measured on a cold browser cache: the first load transfers roughly 140 MB of world data across about 1,150 requests, and the first drawn frame arrives after around a minute. After that the data is cached and a run starts in seconds. A stable connection matters more than a fast one.

For offline play, the official Windows build is about 600 MB and is linked from the game's own page. We do not mirror it here — it is not ours to host.

When it goes wrong

Troubleshooting: black screen, no WebGPU, too many players

These are the four failure states you can actually hit, and none of them is your fault. The client is unusually good at telling you what happened — as long as you know where to look.

1. “This browser has no WebGPU. The world needs it.”

This is the client's own message and it is accurate: your browser cannot provide the API the renderer needs. Update to a current Chrome, Edge or Safari 26+, then reload. On Linux Chrome you may need chrome://flags/#enable-unsafe-webgpu. Firefox needs dom.webgpu.enabled set in about:config.

2. WebGPU exists but there is no usable GPU adapter

This is the laptop case and it is the most confusing one, because the browser reports WebGPU and still refuses to start. Chrome will only offer WebGPU on the GPU its compositor is using, so a laptop drawing on integrated graphics can find no adapter even with a capable dedicated card sitting next to it. Fix it by telling Windows to run your browser on the high-performance GPU (Settings → System → Display → Graphics), then restart the browser. On any platform, chrome://gpu explains exactly why WebGPU is disabled.

3. A black canvas that never draws

Before assuming a bug, give it time: on a cold cache the game streams about 140 MB before the first frame, and the client shows its own loading screen with artwork and a progress bar while that happens. If it stays black well past a couple of minutes, check the browser console — the client logs its boot failure there. It also instruments its own GPU pipeline creation and, if the graphics device is lost, saves a crash report you can read back at localStorage['rogue.gpuCrash']. On weak Android GPUs this is usually a driver crash, not the game.

4. “Too many people are playing!!!”

Not a browser problem at all. The host that serves the game enforces a daily request limit, and when it is exceeded the game page shows that message with links to the Discord and the Windows download instead of a network error. The game logic runs on your machine, so nothing is lost — wait a few minutes and reload, or use the Windows build.

Where Azeroth Survivors sits among browser games

It belongs to the survivors-like family — the genre Vampire Survivors popularised, sometimes called bullet-heaven — with two twists that make it unusual. The first is the setting: instead of a gothic horror map, you are dropped into recognisable World of Warcraft zones with their real creature families and their named bosses. The second is the delivery: a genuinely 3D client, compiled to WebAssembly, running in a browser tab with no install and no account.

That combination is why it spread the way it did — around 300,000 views across community videos in its first week against no official trailer at all. If you already like survivors-likes, the appeal is the same loop with far more geography to it; if you have never played one, it is a free and unusually low-friction place to start.

Azeroth Survivors — play free

FAQ

Azeroth Survivors FAQ