The Silver Hand

"Aeon."

The name is spoken calmly, which belies the urgency behind it. We are deep into the final phase of the Lei Shen encounter, and the boss is casting Thunderstruck on the raid. Most of our raiders are badly positioned, and this is going to be a rough one. My raid leader has said my name because he has made a calculation, in the half-second available to him, that there is one person on this roster who can close the gap between what is about to happen and what should happen instead.

He doesn't know that I've already pressed the necessary button. I cast Devotion Aura a half-second before he spoke.

The neural impulse that carried my name from his brain to his mouth started at the same moment I was already in motion – he was still processing that something needed to happen while I was processing that it was already done. The raid will take less damage. The fight will continue. Nobody needs to know why.

This is what it means to be a paladin.

I am a paladin. That's the sentence I want to start with, because it is both very simple to say and complex to unpack.

I have played every class in this game. In the Classic timeline alone, I have maintained multiple characters at the raiding level across different raid teams, and at various points across that timeline have held what you might call a "main" on a rogue, a hunter, and a paladin simultaneously, distributing them across different groups based on what each team needed. I know the rogue toolkit the way a craftsman knows a blade he's carried for years. I know the hunter's rhythms, the movement, the patience and the pivot. I understand how these classes work not just as kits but as identities – as ways of moving through a fight and through a world.

Playing many classes is the best way to understand any one class. Often, we assume that the classes are interchangeable from the outside in the same way that roles on a team look interchangeable – somebody deals damage, somebody absorbs it, somebody puts it back. But the how of it differs in ways that compound over thousands of decisions. A ret paladin and an arms warrior both wear plate armor, both swing two-handed weapons, both want many of the same stats. But they are not the same. The warrior comes alive in the final moments of a fight, cleaving through weakened enemies during execute phase. The paladin front-loads, stacks cooldowns, erupts in a thirty-second window of concentrated devastation and then sustains through the back half with steady, deliberate output. Different shapes of the same role. Different temperaments. And where most raid teams struggle is assuming that they are fungible assets, to be swapped at a whim.

You learn this by doing it. And doing it across classes teaches you, eventually, that the one you keep returning to is not a preference. It is a reflection of your identity, expressed through the medium of a video game class.

I am a paladin.

The first paladin I ever played was in Final Fantasy IV. The main character is Cecil, who begins the game as a dark knight, and is forced to travel a long road of penance and arrives, on the other side of it, in white armor. His class changes to paladin – a word with which I was unfamiliar at the age of 9 – and I understood it generally as a warrior who heals. The framing made sense to me before I could have told you why. Then came Agrias in Final Fantasy Tactics, a holy knight in title but paladin in function – a soldier who fights to protect and defend the princess. Soon after came the paladin units in Warcraft II, cavalry with access to holy magic, built as much for defending allies as for breaking enemies.

The shape was consistent before the name was. Fighter and healer and defender, collapsed into one. Versatile – not in the sense of doing many things adequately, but in the sense of doing what the situation requires, which is a different and more useful thing.

World of Warcraft deepened all of it. Diablo II had introduced me to auras – the idea that a paladin's mere presence could alter the battlefield, that proximity to your allies was itself a form of service. You didn't have to activate it. You didn't have to aim it. You just had to be there, committed, and everyone around you was better for it. That struck something. The pattern continued with Warcraft III – the Paladin hero has an ability called Devotion Aura, which confers additional armor to every friendly unit in range. That aura has since been deprecated in WoW as a passive mechanic, replaced by an active ability – that through sheer force of will, you can briefly protect your raid group from a portion of incoming damage.

But I'm getting ahead of the story.

My paladin history in World of Warcraft begins properly at the start of The Burning Crusade, when I leveled one on Korgath and found myself initially raiding with it through T4 and T5 content as a healer, then into T6 as a protection paladin. The tank who built around spellpower. The one who held threat on waves of enemies in Mount Hyjal through a combination of Consecrate and sheer mechanical stubbornness, holding waves of undead on the front of my shield as if it were made of superpowered fly paper.

But if I'm honest – and this piece requires honesty – the paladin was already my answer before I had finished the question. There is a version of class selection that is purely mechanical: this class does this job, the job is needed, therefore this class. I've done that version. I've played specs and classes I'd never have chosen freely because a team needed the role, and I don't regret it, because playing things you wouldn't have chosen is how you learn what choosing means. But paladin was never a strategic deployment. It was a homecoming I kept making before I understood that's what it was.

In Wrath Classic, I main-tanked for Starcaller – the raid team Clover and I built from scratch – on a protection paladin. I needed that for a very specific set of reasons: I needed a class with the versatility and difference-making capabilities of a paladin, and I needed to play a class that I had thoroughly internalized the heuristics so that I could turn my attention outward to the raid. In my two other teams where I played, I was a rogue and a hunter. The three classes have lived side by side in my roster across every expansion since: rogue, hunter, paladin. I think of them as a triad, three expressions of something coherent underneath. The rogue is planning and precision – the player who has already decided what's going to happen before the pull even starts, and who suffers most when circumstances deviate from the plan. The hunter is mobility and awareness – wide-field, adaptable, comfortable in the space between structure and chaos. The paladin is the one who stands between everyone else and whatever's coming.

Paladin is the tip of the spear. The other two are what makes the spear possible.

Right now, in Mists of Pandaria Classic, I have four paladins at the raiding level. Three of them run in different raid groups, covering different nights, different teams. The fourth exists as a laboratory – a character where I can try things, test adjustments, see what improves before propagating a change to the others. I'm not sure what to call this except dedication expressed in the only way that makes sense at this level of the game.

I am a paladin.

Some people are happy to play a class in WoW because it’s “meta” or because the playstyle feels good, but that’s not enough for me. I love paladin because it is a class defined by its origin story.

After the First War – after the Horde tore through the kingdom of Stormwind and left it in ruins – Archbishop Alonsus Faol of the Church of the Holy Light looked at what remained and saw a problem. His priests were healers, scholars, cloth-wearers. They were spiritually formidable, but physically unsuited to the kind of warfare that was coming. What the Alliance needed was something the world of Azeroth did not yet have: people who could fight and heal and defend simultaneously, who felt the calling of the Light as something that demanded action, not contemplation.

The Order of the Silver Hand was his answer.

Warriors who saw responsibility and felt obliged to answer it. Not warriors who wanted glory. Not warriors who sought revenge for what the Horde had done to Stormwind – though the wounds were real, and the grief was real, and the anger was understandable. The best of them – Uther Lightbringer, Turalyon, those who defined what the class was meant to be – fought because fighting was what the moment required in service of something larger than themselves. To defend. To protect. To pay, in sweat and sacrifice, whatever cost was necessary to make sure the people behind them were still standing when the fight was over.

This is why Arthas is a cautionary tale rather than a disqualification.

He is the Silver Hand's greatest failure and most instructive lesson. A paladin who let his grief and his fury rewrite his sense of what he was fighting for. Who substituted vengeance for purpose and found, at the end of that road, something that bore no resemblance to the man who started walking it. The Order doesn't stop mattering because Arthas fell. The Order means more, actually, because it shows what the standard is and what it costs to abandon it. Uther died before he would follow Arthas into Stratholme. Turalyon spent decades in the void between worlds, holding the line, and came back. Yrel took up the mantle on a different world, fighting because her people needed someone to.

The class produces a particular kind of person. Or perhaps it attracts them.

I am a paladin.