Hey everyone, I’m Warren West. I’ve been playing World of Warcraft for over fifteen years as a progression raider, tank player, and theorycrafter, and I’m the person behind everything published here on paehl.com. My goal with this site is simple: take complicated encounter mechanics, messy simulation data, and sudden balance passes, and translate them into practical, battle-tested playbooks that help you and your guild actually kill bosses and time keys.
My Progression Background and In-Game Journey
Over the years, I’ve served as a frontline tank, raid leader, and tactical caller across several competitive rosters. I learned early on that success in high-end PvE doesn’t come from treating a boss fight like a static checklist. Live combat is chaotic. Positioning shifts, someone misses a kick, or a mechanic overlaps unexpectedly.
Because of that, I approach every encounter and dungeon as a dynamic puzzle. I look at empirical combat logs, review damage intake spikes, and build strategies around situational adaptability. My focus is on what actually happens during a pull—how we position the boss, how we sequence defensives, and how we keep the group calm and focused during progression.
How I Break Down Each Role
When I write a guide or build a strategy sheet, I look at the fight through the specific demands of each combat role. The table below outlines my primary analytical focus and what I aim to deliver for you:
| Role | What I watch | What you get |
| Tanks | Boss position, pull pace, where the group stands | Position maps and pull orders my own group runs |
| Healers | Burst windows, dispel order, mana left at the end | Cooldown sheets matched to boss timers |
| Melee | Uptime, kicks, dodging frontals without dying | Priority lists built for real movement |
| Ranged | Bait duty, spread discipline, casting on the move | Spread maps and cooldown plans that survive pugs |
My Philosophy: Live-Tested Over Pure Theory
I have a strong rule for everything I put on this site: if I haven’t tested it in live combat or verified it in real logs, I don’t write about it. Raw simulation profiles are useful benchmarks in a vacuum, but they assume zero movement, perfect latency, and no mistakes. Real progression involves panic recoveries, movement constraints, and imperfect play.
Every guide, rotation checklist, and route blueprint I publish is tested directly in live Mythic raids, high Mythic+ keystones, or public test realms. I strip out filler text, generic lore summaries, and corporate fluff. I want you to be able to open my notes during a quick break between pulls, see your exact assignments and talent strings, and get straight back to the fight.
The Standards I Follow on This Site
Whenever I publish new material on paehl.com, I hold myself to four personal benchmarks:
- Tested on my own nights: every route, build and call on these pages survived a live raid or a timed key before it got published.
- Fixed fast after hotfixes: when Blizzard moves numbers, I re-test and update within days, not someday.
- Built for breaks between pulls: short sections and clear calls, no lore essays standing between you and the boss.
- Reader-tested too: logs and routes you send in get tested the same way, and the good ones make the page.
