Video summary

Blizzard Isnt Making Your Classic Plus | Xaryu Reacts

Main summary

Key takeaways

Business

Business-focused summary (Classic Plus / Blizzard execution lens)

Blizzard isn’t being “asked” to build what classic fans want—it needs Classic Plus to make business sense while also creating a compelling product. The core tension is that community expectations splinter into multiple “classic plus” interpretations, forcing Blizzard to choose an audience focus (and say no to others) while still attracting enough players to justify ongoing investment.

What Classic Plus must optimize for

  • ROI / business case first: Classic Plus needs to “get something back” for development spend (not just “fan service”).
  • Long-term value over short-term extraction: “Doing right by the customer” is argued to support long-term retention and revenue more reliably than short-term monetization pressure.
  • Broader appeal than a single niche: It must work across segments, including:
    • Vanilla purists
    • Season of Discovery-style experimenters
    • Retail convenience-seekers
    • Hardcore/difficulty players
    • Casual/solo-focused players

Market/user-segment reality check (why “one Classic Plus” is hard)

Classic Plus is framed as not one product, but a bundle of conflicting desires:

  • Vanilla purists: original feel with minimal mechanical change
  • Season of Discovery: new classes/abilities/roles; more experimentation
  • Retail players: modern conveniences/account systems
  • Hardcore: more difficulty modes for dungeons/raids
  • Casual/solo: more quests, improved professions, exploration, self-sufficiency

Product strategy principle: “Saying no” / selecting a target

A key product/leadership theme is deliberate scope control:

  • Trying to make one release satisfy every MMO preference leads to “no one happy.”
  • Classic Plus should be intentionally designed for a primary segment (e.g., an “old school relaxed chill grind MMO”), accepting that it will exclude others.
  • If Blizzard tries to attract everyone, the feature set risks drifting into “modern competitive” systems (e.g., Mythic Plus/Arena/Rated Battlegrounds analogs), which may violate the classic identity.

Operating model: ongoing cadence vs. “one-and-done”

Classic Plus is framed as an iterative, long-running content system (similar to how Retail sustains interest):

  • Don’t expect every “good idea” on day one.
  • Introduce major features over phases, such as:
    • New dungeon/raid “headlines” later (e.g., “Scarlet Enclave” then “Kazon Crypts”)
    • New race/class later as distinct content phases
    • Unfinished vanilla zones as another long content phase
  • This sustains returning players and gives Blizzard more opportunities to refine based on feedback.

Example operational philosophy: “course correction” capability

A strong execution recommendation is fast responsiveness after launch:

  • The speakers want Blizzard to fix mistakes quickly (“course correct”), not defend wrong decisions.
  • RuneScape is used as a benchmark:
    • community feedback triggers rapid reversal/redesign
    • next-day communication is favored over week-long delays

Community governance / co-creation (best-case vision)

One participant proposes an extreme community-driven model:

  • Start with “zero changes” / the classic era base
  • Add a polling/voting mechanism for future content decisions
  • Suggest voter gating (e.g., participation thresholds like OSRS) to reduce noise/bad input
  • Goal: increase the odds the game improves over years, with a population trajectory that can rise rather than decline

Risks and expectations management

The discussion expects some failures—bugs, balance issues, unwanted convenience features, class changes, or monetization backlash (e.g., speculation about paid mounts). Because of that, the acceptance criterion isn’t “100% correct,” but:

  • “What’s the ability to adapt and adjust after feedback?”

KPIs / targets mentioned

No explicit business metrics (revenue, CAC, LTV, churn, growth targets) are provided. The measurable performance concept is implicit:

  • Population over time / retention curve
    • Desired best-case: launch “okay,” then patch-to-patch improvement leading to a long-term upward or stabilizing player graph
  • Cadence effectiveness
    • “Reasons to keep coming back” via phased updates

Actionable recommendations / playbooks implied

  • Build a business-justified roadmap: align Classic Plus investment with expected long-term returns.
  • Use segmentation-driven scope: explicitly choose a primary target audience and accept exclusions.
  • Adopt phased release planning: avoid “everything day one”; ship in content waves.
  • Create a rapid feedback loop:
    • gather community signal after launch
    • reverse mistakes quickly
    • communicate changes transparently
  • Consider community input mechanisms (voting/polls) for longer-term direction—potentially with participation gating to limit bot/noise impact.

Concrete examples cited (content candidates)

  • High elves / ogres / new classes / new raids / new zones
  • Named content areas:
    • Scarlet Enclave
    • Kazon Crypts
  • Mage-focused examples requested:
    • deep freeze / Ice-Frost style abilities
    • alter time
    • blazing speed
    • stealth wish
    • bubble / AoE polymorph concept
    • “instant-cast chaos bolt” style rework (presented as a speculative wishlist)

Presenter / sources mentioned

  • Xaryu Reacts (video framing/title)
  • Azeroth United (source of the referenced video)
  • Denithar (source/person referenced within that video)
  • Benchmark/execution/comms reference: Old School RuneScape / RuneScape devs

Original video