Raid notes, arena habits and talent math from Azeroth

half-waif

Ask a question

Notes from the queue: raids, arena and talents

A working diary of one WoW player: how raid nights get planned, which talents earn their slot, and what makes an arena set go smoothly.

⇨

start here

Raid nights

How a raid evening gets planned, from consumables to who calls the pulls.

⇨

Raid prep notebook

Group content

Dungeon keys, pacing and routes explained the way I explain them to friends.

⇨

Start here

Arena habits

Small habits in positioning and cooldown use that decide close matches.

⇨

Talent tables

About the writer

Who writes these notes, what I play and how the site is put together.

⇨

Meet Kelly

Raids • Mythic+ keys • Arena • Talents • Transmog • Gold • Raids • Mythic+ keys • Arena • Talents • Transmog • Gold • Raids • Mythic+ keys • Arena • Talents • Transmog • Gold • Raids • Mythic+ keys • Arena • Talents • Transmog • Gold •

about the diary ⇨

one player, a lot of reset days.

Every post here comes from time spent in Azeroth: wipes on new bosses, talent trees rebuilt at midnight, arena sets that fell apart in the first thirty seconds.

I write down what actually helped, so the next raid night or key starts with a plan instead of guesses. Pick a guide from the grid below or begin on the start page.

Three weeks of learning raids from the passenger seat

Last season I hit a wall that had nothing to do with gear. My character was fine; my map of the raid was not. I knew the first two bosses by feel and the rest by rumour, and every attempt past that point turned into a lesson I could not keep because the group around me kept changing. So I tried something different for three weeks and kept notes. This is the short version.

Week one: watching instead of pulling

The first thing I changed was my job during the run. Instead of trying to play perfectly while also learning the encounter, I let someone who already knew the order of events lead, and I watched. It sounds passive, but it was the most active studying I had done in months. I paid attention to where the group stood when the room filled with adds, which cooldown went out before the big hit, and how long the quiet stretches between mechanics really lasted.

By the end of that evening I had a page of scribbles: positions, timers, who covers which interrupt. None of it was clever. All of it was information I had been missing for a whole season because I was always too busy reacting to collect it.

I also learned to read the room before the room read me. Raid layouts repeat their ideas: a safe corner, a moving hazard, a phase where the whole group stacks. Once I started naming those ideas, new bosses felt less like strangers and more like variations on fights I already understood.

Week two: borrowing a route

Once you have seen an encounter solved cleanly, you start noticing how much of raiding is route planning. The order of bosses, the trash you skip, the spots where you reset your cooldowns, the moment you drink before the next pull. In my second week I went looking for a way to run those routes with people who treated them as routine, and that is how I came across the idea of a WoW Boost. The label undersells the part I cared about: an experienced group walks the content with you, and you keep your own character in the middle of it, taking your own turns and seeing the fights from the inside.

What I took from it was a template. A clean run has a rhythm, and rhythm is teachable. I wrote the rhythm of each fight as three short lines, what happens, what I do, what I check afterwards, and taped that list beside my monitor.

Week three: taking the lead myself

The third week was the test. I organised a small group of friends, opened the same raid, and tried to explain the first boss before we pulled it. The explanation took ninety seconds. The kill took one attempt. Nothing about my gear had changed since the wall I hit earlier; what changed was that the people around me now knew what the room was going to do, because I did.

Teaching it out loud exposed gaps, too. I realised I could not say who should take a particular debuff, so we settled it before the pull instead of arguing about it after the wipe. That small rule saved us several minutes on the next two bosses.

There was a quieter benefit as well. Two of the friends I brought along had been avoiding raids because they feared holding everyone up. After one calm, well-explained kill they asked when the next one was, and the group has met every week since. A shared plan makes a raid feel smaller and friendlier than the loot tables and leaderboards suggest.

What I would tell a friend who is stuck

If your progress stalls and the gear is not the reason, look at the information you carry into the fight. A few things worked for me and need nothing but a notebook:

  • Watch one full clear before you try to play one, and write down timers rather than impressions.
  • Turn every boss into three lines you can read at a glance during the downtime.
  • Decide the small jobs, such as interrupts, dispels and debuff soaks, before the pull.
  • Explain the first fight out loud to someone else. Whatever you cannot explain is what you do not know yet.

None of this replaces practice, and nobody is going to learn an encounter without a few wipes. But a wipe teaches far more when you walked in with a plan, because you can see exactly which line of the plan failed and fix that one line.

If you want to see how I handle the character side of this, the talent tables on this site show the builds I settled on for raiding, and the start page lists the older posts in a sensible reading order. Whatever route you choose, keep your notes short, keep them honest, and bring them to the next reset.

latest guides

⇨

reading order

questions welcome

Stuck on a boss? Send me the question.

Ask a question