The Windows Central interview with the World of Warcraft: Forever team — lead game designer Tim Jones and lead software engineer Nora — was published on September 22, and it contains the sharpest public articulation yet of three things the beta community has been arguing about since day one: class viability, difficulty, and what "new lore in a Classic world" actually means.

"Every single one of our 27 talent trees is now viable"

Jones's class design commitment is the headline:

"Every single one of our 27 talent trees is now viable for all content in WoW: Forever. That's one big class design goal. That doesn't mean they're all the same... or all equal. They have strengths and weaknesses. But they're all worthy to bring. None are so powerful that you'll stack your raid with them either."

Nora made it concrete with the most contested spec in Classic history: "You can be a Ret Paladin in raids, you can Seal twist." The explicit contrast is the original game, where Prot Paladins could not tank serious content because they lacked a taunt.

This is a stronger claim than "we rebalanced things." It is a promise that the Classic ecosystem's load-bearing assumption — that some specs are simply not invited — is being removed on purpose, while retaining enough spec asymmetry that raid composition still involves decisions. Whether "viable" survives contact with an optimizer community that spent two decades building spreadsheets precisely to find the non-viable specs is the open question; the beta's class feedback threads are where that test is running.

Hard, but not 100 wipes

On difficulty, the two halves of the statement are equally deliberate. Raids "should be difficult" — you will need potions, buffs, reputation grinds, and research on boss mechanics. But: "We're not going to stomp your face into the ground."

Jones's formulation of the target: "Over-prepare and crush the content, that's what Classic players want to do." No one should be attempting a boss a hundred times; a group that formed properly and did its homework should be "on the road to success."

This is consistent with the raid-size and cadence promises from the separate MKAU interview we covered in our raid-tier breakdown — consistent 10- and 20-player content every patch, Onyxia as the lone 40-player raid — and it draws a clean line between Forever and retail Mythic progression. The pitch is not "easier than retail"; it is that difficulty should be solved by preparation, not by wiping as a learning strategy.

"A new continuity... adjacent timelines"

The lore section is the part with the longest shelf life. Asked how Forever can add a brand-new playable race and new zones to a world whose history players know by heart, Nora was direct:

"This is a new continuity. We're starting from the same place. Think of adjacent timelines. Some things might be a bit different... we're not going to do something that is super divergent, like, stopping Arthas from becoming the Lich King for example. Or that Jaina is secretly a Dreadlord... but who knows?"

The examples given show the method working outward from the blanks in the old world:

• The Skyborne tell the story of Eldre'Thalas and Dire Maul — a plotline Classic never fully fleshed out.
• River Glades is a zone built on a landmass that "existed in the classic map... but there was nothing there."
• The weird gate in Azshara becomes Timbermaw Hold; Old Ironforge is name-checked as an unanswered question the team wants to exploit.

This is, quietly, a different approach than any previous Classic product. Classic Era preserved a timeline; Forever is declaring a parallel one that starts identical and diverges only where the old game left empty space. For lore-sensitive players, the operative guardrail is Nora's: no divergences at the level of "stopping Arthas." Everything else — including what is inside Old Ironforge — is fair game.

Content at every level, not just 60

The most forward-looking quote in the interview concerns what Forever adds after launch. Jones:

"We might add an update where we put in a new zone designed not for level 60, but for level 27 to 32 for example, with a new dungeon. The best way to experience that would be to make a new character. It's not all about level 60, we're going to serve across all levels."

This would be genuinely novel for a Classic-shaped product: Classic Era never added leveling-range content after launch, because the vertical treadmill made it pointless. Forever's permanent level 60 cap plus its account-wide Legacy system changes the math — a mid-level zone is not wasted content if the design intends you to experience it on a fresh character, and the Legacy perks give you account-level reasons to do so. Combined with the roadmap's Spring 2027 "new quests and playable area" entry, mid-level zones look less like a hypothetical and more like the actual shape of the first post-launch update.

Retail might borrow the campfire

One quote that got less coverage than it deserves, given where retail's design conversation is heading. Jones, on the cross-pollination between the Classic team and retail:

"I could see them borrowing the camping system from us very easily, and perhaps connect it to Player Housing? I would love some day to maybe take Player Housing and bring it into the Classic world."

Nothing announced — but it confirms the camping system is being watched as exportable design, and that Classic-style housing is at least a live internal idea. Worth remembering the next time someone declares the Classic and retail teams never talk.

The audience question, in context

It is worth reading this interview against the same week's noise. Community-adjacent developer posts argued that "convenience is the death of the journey" and that Classic players — not retail players — are who Forever is for. The leads' official framing is broader: the world-as-main-character philosophy, spec viability for everyone, possibly even content pitched at level-27 characters. Both messages describe the same friction-forward design. The difference is that the interview is a pitch to the curious — including retail players — while the individual posts read as a gate. Only the interview is an official position.

For the beta-state bugs and the weather patch referenced in the same coverage window, see our beta roundup.