A class buff can make your next dungeon easier. It cannot automatically make you enjoy the character you bring into it. That distinction is where our team starts with WoW Forever class design, especially for players deciding whether to keep investing in a main or wait for another round of changes.
The November 19, 2026 episode of Catching Up on Classes brought host Countdown To Classic together with designers Aidan Moon and Kris Zierhut for a class-focused conversation. We are using that discussion as the starting point for a practical question: how should players approach class choice while the game's design continues to develop? This is our assessment, not a confirmed patch preview.
Before committing more WoW Forever Gold to gear, professions, or a possible reroll, we would separate three concerns: whether a class feels enjoyable, whether it can perform your intended role, and whether its current problems have a clearly defined solution. Treating those as one question makes an expensive decision look much simpler than it really is.
What the Class Discussion Means for Your Main
Our team would not turn a developer conversation into a shopping list of future buffs. A designer acknowledging a problem is useful. A proposed solution is more useful. Neither tells us exactly how a character will perform after implementation.
That distinction matters most when a player is already frustrated. Hearing that a specialization is being discussed can feel like permission to keep waiting indefinitely. Sometimes patience makes sense. Sometimes it merely delays the realization that the class's basic combat rhythm is the problem.
We would read class-design commentary through three separate lenses:
| What you are evaluating | What it can tell you | What it cannot establish alone |
|---|---|---|
| Design philosophy | Which qualities the team wants to preserve | The strength of your next build |
| Acknowledged problems | Where developers recognize friction | A guaranteed fix or release date |
| Specific proposed changes | How a solution might affect gameplay | Its final implementation or results |
| Published, implemented changes | What you can actually test | Long-term balance stability |
Our practical rule is straightforward: make today's commitment around today's playable experience, then leave enough flexibility to respond to meaningful changes.
That does not mean ignoring developer intent. It means using intent to understand direction rather than treating it as a replacement for finished mechanics.
For anyone searching for the next strongest class, this is the uncomfortable part: a discussion about design quality cannot give us a reliable future tier list.
Class Identity Should Survive Better Balance
Blizzard's published design outline emphasizes recognizable strengths and weaknesses, tactical combat, and classes that are approachable without losing depth. It also describes the aim of supporting different Paladin roles without erasing the class's distinct character. Those are established design goals, not newly confirmed promises from the November 19 episode.
Our reading is that successful balance should give players credible reasons to bring different characters, without requiring every character to solve the same problems in the same way.
We would be concerned by either extreme. A specialization should not need an apology before every invitation. It also should not need a copy of every other specialization's tools to become desirable.
A weakness needs room for a response
Consider a hypothetical caster that loses damage when forced to move. We would ask whether good positioning, timing, or coordination can reduce that loss. If the answer is yes, the limitation can create satisfying decisions.
If ordinary encounters repeatedly prevent that character from contributing, with little opportunity to respond, we would treat that as a usability problem.
The same distinction applies to melee downtime, resource pressure, and defensive limitations. Our standard is not perfect comfort. We want constraints that reward learning rather than constraints that make the player feel like a spectator.

Utility needs an honest evaluation
Our team would give control, emergency support, and survival tools their own space in a class assessment. We would also refuse to use them as a blanket answer to every damage complaint.
"You bring utility" is not a complete evaluation. Which utility? Where is it useful? Does the group need it? What does using it cost?
Those questions produce better recommendations than either dismissing support tools or pretending they excuse any performance gap.

Why a DPS Ranking Cannot Choose Your Class
We would use a damage ranking as evidence for a specific question, not as a character-selection screen.
A ranking can help investigate output under defined conditions. Our next step would be to check the conditions: encounter type, equipment, group composition, player experience, and the version being measured. Without that context, a precise-looking number can invite a very imprecise decision.
For class selection, we prefer three separate assessments.
- Output: Can the character deliver enough damage, healing, or threat for the content you intend to attempt?
- Execution: Can you reproduce that performance while handling movement, targets, resources, and mistakes?
- Enjoyment: Do you want to repeat those decisions throughout your normal week?
A player might love a demanding rotation but dislike managing a pet. Another might enjoy supporting a group while finding a stationary damage cycle dull. We would not expect a numerical ranking to settle either preference.
Our advice is to describe the complaint before looking for a replacement. "My damage is low" needs investigation. "I dislike spending most fights chasing targets" already tells us something useful about the next character to test.
There is also a difference between struggling to learn a class and disliking it after learning it. We would allow time for the former. We would be cautious about prescribing more practice as the answer to the latter.
A stronger specialization can still be the wrong place to spend your evenings.
How We Would Choose a WoW Forever Class Now
Our starting point would be the content a player expects to repeat, not the most impressive clip they watched.
Someone planning relaxed questing needs a different evaluation from someone filling a fixed group slot. A player interested in PvP needs to examine the decisions they enjoy making against other players, rather than borrowing a recommendation written for dungeon damage.
We would use this selection framework:
| Your main goal | What we would prioritize | What we would test before committing |
|---|---|---|
| Solo questing | Comfortable recovery and manageable mistakes | Several ordinary pulls, including one that goes badly |
| Regular dungeon groups | A role you willingly take responsibility for | Target changes, recovery, and group coordination |
| Organized damage dealing | A combat rhythm you can sustain | Movement, resource use, and unfamiliar mechanics |
| Healing | Enjoyment of reactive decisions | Recovering from mistakes without losing interest |
| Tanking | Willingness to guide and stabilize pulls | Threat management, positioning, and communication |
| PvP | A preferred way to create pressure | How the class responds when its opening plan fails |
| Limited weekly sessions | A satisfying routine | Whether normal progress feels rewarding |
These are testing priorities, not claims that one class automatically wins each category.

Choose a role you want to perform
We would be wary of picking a tank or healer solely to solve a group shortage. Helping friends is a reasonable motivation, but it should not hide a genuine dislike of the job.
Ask what part of the role sounds satisfying. Is it controlling the pace? Recovering a dangerous pull? Planning damage windows? Keeping track of several threats?
If none of those decisions sounds appealing, a convenient group slot may not compensate.
Test the frustrating moments too
A trial should include more than a clean fight against an easy target.
Our preferred test would include an interrupted plan: an unexpected enemy, a moving target, a missed cooldown, or a pull that lasts longer than expected. The question is whether recovering feels engaging or irritating.
We would also check ordinary downtime. If a player hates the moments between successful fights, that frustration deserves attention before a larger commitment.
Are Hybrid Classes a Safer Long-Term Investment?
Our team would describe a hybrid as an opportunity to explore different responsibilities, not as insurance against balance changes.
The attraction is understandable. A player who is unsure about a long-term role may value the possibility of trying another job without abandoning the character's identity. That flexibility deserves consideration.
We would still budget for the transition. Before recommending a second role, we would check its equipment needs, talent choices, keybinds, and learning demands. "We can switch" is the beginning of that assessment, not the end.
A useful question is: would you genuinely enjoy the alternative role, or do you only like knowing it exists?
If a player wants to deal damage and has no interest in tanking or healing, we would not push a hybrid simply because its character sheet suggests more options. Unused flexibility should not outweigh a combat style they actually enjoy.
We would also separate owning a support tool from wanting a support responsibility. An occasional emergency action can feel rewarding. Being expected to monitor that situation every fight may feel very different.
Our recommendation is to choose a hybrid when at least two of its possible roles appeal to you enough to practice. Otherwise, evaluate the role you intend to play on its own merits.

Should You Reroll or Wait for Class Changes?
We would make this decision around the source of dissatisfaction and the cost of testing an alternative.
Waiting can be sensible. Waiting without a specific reason is much harder to defend.
Keep investing when you enjoy the core loop
If the rotation, resource system, and role still feel satisfying, we would hesitate to abandon a character because of a disappointing ranking or one rough evening.
We would first review the problem under comparable conditions. Then we would make a small improvement plan: practice a mechanic, review equipment choices, or test a different approach.
That gives continued investment a purpose. It also creates a clearer basis for judging later adjustments.
Our team would favor reversible progress while uncertainty remains. Continue learning and participating, but scrutinize purchases or commitments made solely on the assumption that a buff is coming.
Pause major spending when the proposed fix is specific
We would consider a temporary pause if a published proposal directly addresses the mechanic a player dislikes.
The connection needs to be concrete. A change to resource availability might address repeated empty periods. A talent adjustment might change an awkward sequence. A general statement about improving a class does not provide the same basis for waiting.
Before pausing, write down what would count as success. If the change arrives, test that condition instead of relying on the excitement surrounding the patch.
We would also give the pause a review point. An indefinite wait can quietly become a routine.
Try another character when the basic gameplay is wrong
If the complaint is about the class's fundamental rhythm, we would start testing alternatives rather than waiting for higher numbers.
A buff might make an unpleasant sequence more rewarding. It may leave the sequence itself untouched.
There is no need to turn that test into an immediate main swap. Our preferred approach is a limited trial with a clear question: do we enjoy this resource system, this range, or this responsibility more?
Keep the original character intact while answering it. Curiosity is a better reason to start an alt than panic.

What We Would Watch in the Next Class Update
Our expectations are analytical rather than predictive. We would judge future adjustments by whether they make the intended gameplay work more convincingly.
The first question would be what the change solves. A damage increase, a smoother leveling sequence, and a less awkward talent choice can all be useful, but they answer different complaints.
Next, we would check where the benefit applies. A change that helps one encounter pattern should not automatically reshape our recommendation for every activity. We would want the advice to name the content and the condition.
We would then examine the cost. Does the improvement require different equipment, additional preparation, or a more demanding sequence? That tradeoff may be worthwhile, but players deserve to see it before rebuilding around the change.
For preparation, we would favor useful flexibility over speculative stockpiling. Our approach to WoW Forever Items would be to organize current upgrades and credible alternatives around an actual role, rather than fill storage for every build mentioned in a discussion. A possibility becomes a plan when the mechanics give us a reason to act.
Before the next substantial investment, our team would write three short notes: what we enjoy about the current character, what specifically needs improvement, and which available alternative we want to test. That makes the decision smaller and easier to revisit.
If the current class still delivers the moments you log in for, keep playing it while reviewing confirmed changes. If it does not, test another character through ordinary fights and difficult recoveries. Keep the one whose decisions you want to make again tomorrow.