The starting setup in this observation
The original browser client displayed v0.122.0 (508416ff) on October 27, 2026. Human Warrior was selected, Elwynn Forest was available, and Enter Elwynn Forest was clicked. The observation reached Level 3; it did not cover a boss encounter or a completed zone.
The steps below describe that short run. They are useful for recognizing the opening sequence, but do not establish a strongest class, an optimal build or cards that every player will receive.
Load the zone, then move to begin
After loading, the character appeared in the zone with Move to begin in the center of the screen. The timer showed 00:00 and the HUD’s next-boss marker showed 03:00.
W was pressed once. The run timer started and the game announced The Defias Uprising with an instruction to survive the onslaught. No attack input was sent, and the kill counter was observed increasing to 1 before the first level-up. That is an observation of this starting setup, not a test of every class or ability.
If you still see a loading screen rather than the character and start prompt, use loading help. For the rest of the displayed movement bindings, use the menu and controls guide.
Read the first upgrade offer before picking
At timer 00:08, the observed run reached Level 2 and displayed three numbered cards. The offer contained Battle Shout, Whirlwind and Bloodrage. Battle Shout and Whirlwind were labelled Common; Bloodrage was labelled Uncommon. All three were shown as new spells.
Below the cards, the Spells row showed six slots with one already occupied. Each offered card indicated that it would take spell slot 2/6, and the reroll control displayed Reroll 3. These are the values shown in this offer; your cards, rarities and timing can differ.
On a small screen, scroll the table sideways to read every column.
| Card in this offer | Displayed rarity | What to read before choosing |
|---|---|---|
| 1 · Battle Shout | Common | Its description concerned a damage increase and a trigger based on enemies being within a stated distance. |
| 2 · Whirlwind | Common | Its description concerned hitting every enemy within an 8-yard radius. |
| 3 · Bloodrage | Uncommon | Its description concerned building rage through hits and a triggered damage effect. |
Use the description, target pattern and slot count
The level-up screen says rarity affects a spell’s strength. Read the complete description alongside the rarity: a color alone does not tell you whether the effect reaches the targets you expect or serves the same purpose as another card.
Use this short check at each offer. The examples are labels observed in the first two upgrade screens, not a tested ranking of their damage.
On a small screen, scroll the table sideways to read every column.
| Read this | Example from the observation | Why it matters |
|---|---|---|
| Reach or radius | Whirlwind’s Level 2 card stated an 8-yard radius. | Check the stated distance before expecting a nearby effect to hit a distant target. |
| Target pattern | The Level 3 cards described a nearest target, three healthiest targets, or up to two targets. | A single-target effect and a multi-target effect cannot be compared by one damage number alone. |
| Rarity and conditions | The offers included Common, Uncommon and Rare labels, with different triggers and effects. | Read what activates the spell and what its effect applies to. Do not choose by color without reading. |
| Spell slots | The first offer said 2/6; after the choice, the next new-spell offer said 3/6. | Look at the occupied slots and the cost printed on the card before taking another new spell. |
| Remaining rerolls | The control displayed Reroll 3. No reroll was used. | Check your current counter before deciding whether to keep or replace an offer. The spending behavior was not tested. |
Pick a card and verify the spell row
At the first offer, the number 2 key was pressed. The selected card was Whirlwind, and the next observed spell row showed its icon in the second slot beside the starting spell.
At timer 00:14, the run reached Level 3 and offered Bloodthirst, Rend and Shield Slam. The row still showed the two occupied slots. This verifies the first choice and the arrival of another upgrade screen; it does not establish that Whirlwind is the best first pick or that every run will reach those levels at those times.
For your own offer, match the number to the card you intend to choose, then inspect the spell row after the selection. The number 2 selection was tested here; the menu also displays 1 and 3 as card shortcuts. Those two keys were not separately pressed during this observation.
Keep the result in context
This check stops at the Level 3 offer. The 03:00 boss marker was visible at the start, but no boss encounter, reward, complete run, mobile session or Windows session was tested. A single Escape press did not open a pause menu, so this guide does not recommend Escape as a verified pause shortcut.
Use the manual planner to note the cards you actually received and the choice you want to compare next. Your note is separate from game progress; use the game’s save export route before importing or clearing browser data.
Common questions
Will I get these same three cards at Level 2?
That has not been established. Battle Shout, Whirlwind and Bloodrage were the offer in this observation. Read your own offer’s names, descriptions, rarity, slot cost and reroll counter.
Did the first kills require a manual attack input?
No attack input was sent during this observed Human Warrior opening. After W started the run, the kill counter increased before the first upgrade. That observation does not test every class, ability or control.
Should I always select Whirlwind first?
This check verifies that pressing 2 selected the second card and placed Whirlwind in the second spell slot. It does not compare that choice against other first picks or establish a strongest build.
Was the first boss tested?
No. The initial HUD showed a next-boss marker at 03:00, but the observation ended at the Level 3 offer before any boss encounter.
Sources & check notes
Sources reviewed on October 27, 2026. A source review is distinct from a successful gameplay or device test.
- Azeroth Survivors — creator's game page (opens in a new tab)
What this source establishes
Current HTML read on 2026-10-27. It links the Windows RAR and Discord and loads rogue.js with stamp e06ce49391fe. The page includes a WebGPU warning. Reading the page is not a successful gameplay or device compatibility test.
- Original browser client — menu, saves and first-upgrade observation (opens in a new tab)
What this source establishes
Original browser client observed on 2026-10-27; the menu displayed v0.122.0 (508416ff). Test record: original-web-2026-10-27-warrior-first-choice. Human Warrior was selected and Enter Elwynn Forest was clicked. The loaded zone showed Move to begin, timer 00:00 and a 03:00 next-boss marker. One W press started the timer; no attack input was sent and a kill-counter increase was observed. At 00:08, Level 2 offered Battle Shout, Whirlwind and Bloodrage, with six spell slots, one occupied, a 2/6 new-spell indication and Reroll 3. Pressing 2 selected Whirlwind; the next observation at 00:14 showed Level 3 and its icon in the second slot. These were the offers and timings in this one short run, not guaranteed rolls, progression timing or a build comparison. A single Escape press did not open a pause menu. Other movement and shortcut keys were read from the menu or Key Bindings, not separately exercised. Saves UI showed Export Save, Import Save, the hourly/latest-five backup description and an all-progress replacement warning. Export displayed its success message, but no disk file was retrieved or inspected. No import, restoration, hourly backup creation, boss encounter, zone clear, mobile or Windows session was tested.
- Creator's current browser launcher (opens in a new tab)
What this source establishes
Read as static text, without running the client. Confirms third-party frame rejection; WebGPU API, adapter and lost-device checks; current browser guidance; sound activation on user input; saves.js import; and the documented Options → Saves → Import Save path. The query stamp is an asset cache identifier, not a semantic game version. No control bindings, run outcome or Windows save compatibility were established.