How One WoW Quest Became a Classic Design Disaster

Every long-running online game accumulates legends: unforgettable raids, iconic characters, and, occasionally, truly awful quests. In World of Warcraft (WoW), few quests are as infamous as the early-page-collecting epic in Stranglethorn Vale that its creator, former Blizzard designer Jeff Kaplan, later described in remarkably unflattering terms. What began as a bold attempt to make a clever, narrative-driven experience instead turned into a symbol of over-complication and designer hubris.

This article takes inspiration from reporting around Kaplan’s reflections on that quest to look more broadly at how one bad idea made it live, why players remember it so vividly, and what it reveals about MMO quest design. Rather than retelling every anecdote, we will focus on the design principles behind the quest, the pressures of early WoW development, and the lasting lessons that continue to shape how modern online worlds are built.

The Context: Vanilla WoW and the Ambition to Be Clever

When the original version of World of Warcraft launched in 2004, it entered an MMO landscape dominated by systems-heavy games like EverQuest. Blizzard’s mission was to make a more accessible online world without losing the feeling of depth and discovery. That tension—between readability and complexity—defined much of the early design work.

Jeff Kaplan, who joined Blizzard after being recruited from the EverQuest community, was one of the key quest designers on the project. In interviews, Kaplan has described the thrill of being given freedom to experiment: designers were encouraged to push boundaries, link narratives across zones, and create quests that felt more than simple “kill 10 boars” chores. It was in this climate that the notorious Stranglethorn questline was born.

At the time, “epic” content in MMOs often meant:

• Long, multi-step chains that spanned multiple zones
• Rare drops and randomized objectives
• Heavy reliance on grinding mobs for progression
• Minimal in-game guidance, forcing players to ask others for help

The Stranglethorn page quest leaned into all of these trends at once—and then went even further.

The Anatomy of an Infamously Bad Quest

The quest that players still talk about took the form of a book whose pages had been scattered across Stranglethorn Vale. To complete it, players had to gather dozens of uniquely numbered pages, which dropped randomly from a wide variety of enemies in the zone. Only once every page had been collected could the book be reassembled and turned in for the reward.

On paper, this concept sounds intriguing: a broken text waiting to be pieced back together, themed around a hunter’s exploits in a dangerous jungle. In practice, several design choices collided to make this an ordeal:

• High quantity of unique items: Players needed a large set of individually numbered pages, each occupying their own inventory slot.
• Randomized drops: Pages were not guaranteed drops, turning the process into extended grinding.
• Wide distribution: Pages dropped from many different creatures, meaning no clear path to optimize completion.
• Inventory pressure: Limited bag space in early WoW made holding duplicates and extras painful.

The result was a quest that many players either abandoned, completed only thanks to heavy trading with others, or finished years later out of sheer stubbornness. Kaplan himself has since characterized the design as an example of a younger developer trying too hard to be clever without adequately considering the player’s experience.

Why Players Remember It: Frustration as a Shared Story

Despite its reputation, the Stranglethorn page quest occupies a strange place in WoW history: it is both widely disliked and deeply memorable. Frustrating content, when shared by a large community, can become a bonding experience. Players complained, traded pages, told newcomers horror stories, and even built their own workarounds.

Common pain points included:

• Feeling held hostage by RNG: Some pages seemed to drop constantly, while others refused to appear.
• Bartering and spam: Trade chat and general chat were filled with players listing which pages they had and which they needed.
• Sense of sunk cost: After investing hours, many players felt compelled to finish even if the rewards were mediocre.

That shared suffering became part of the cultural memory of “vanilla” WoW. Modern design standards would call it poor quest structure, but at the time, it became another story to tell: “Remember how long it took you to get that one missing page?”

Hubris in Game Design: When Clever Outweighs Fun

Kaplan’s candid later comments about this quest highlight an important pattern in creative work: the temptation to prioritize cleverness over clarity. Designers, especially early in their careers, often want to leave a visible mark—something uniquely theirs that stands out from the pack.

Signs of design hubris that the Stranglethorn quest exemplifies include:

• Overcomplication: Turning what could be a simple collectible quest into a massive randomized scavenger hunt.
• Ignoring friction: Underestimating the frustration of limited inventory, travel time, and low drop rates stacking together.
• Assuming players enjoy suffering: Confusing time investment and difficulty with meaningful engagement.

Modern game UX research and postmortems often emphasize the importance of reducing unnecessary friction while preserving challenge and depth. Blizzard itself has repeatedly acknowledged that many early systems in WoW were more punishing than they needed to be, and that some of that came from designers wanting content to feel “serious” or “epic.”

What the Quest Reveals About MMO Evolution

Looking back at this quest provides a useful snapshot of how MMORPG design has evolved. Over two decades, player expectations and industry norms have shifted in several key ways:

Blizzard’s own later expansions and other developers’ titles have moved away from sprawling, unsignposted collection quests and toward systems that:

• Use clear drop sources for key collection steps
• Group items logically to minimize inventory strain
• Reserve very long grinds for optional, cosmetic, or prestige rewards
• Provide better in-game journaling and quest guidance

In that sense, the Stranglethorn quest becomes a reference point for how not to structure mandatory content in a mass-market MMO.

Player Agency vs. Designer Control

One of the most interesting aspects of this quest’s legacy is how players responded. Instead of passively accepting the pain, they used it as motivation to build social structures and workarounds:

• Organized page-trading circles and guild banks dedicated to storing duplicates.
• Created community spreadsheets and lists of which mobs seemed to drop which page numbers more often.
• Used the quest as an economic driver, selling rare pages on the auction house for significant amounts of gold.

From a systems perspective, this is fascinating: a poorly tuned quest inadvertently generated emergent social gameplay and economic activity. But it did so by frustrating players first and leaving them to fix the experience for each other. Modern games are more deliberate about this kind of social design, using clear systems like shared world events, public quests, and instanced challenges to foster cooperation without relying on pain points to force it.

Lessons for Quest Designers and Live Service Teams

Kaplan’s candid criticism of his own work underscores how valuable internal postmortems and public reflection can be. For current and aspiring designers, the infamous Stranglethorn quest offers several concrete lessons:

1. Test Clever Ideas Against Player Reality

Inventive mechanics are desirable, but they must be filtered through the realities of how players actually interact with the game:

• How many duplicate items will players accumulate?
• How often will they have to travel back to town to clear bags?
• Are the drop rates tuned for an average session length, not an idealized one?

Extensive internal testing and real-world telemetry, now common in live service games, help designers understand where frustration crosses from engaging to exhausting.

2. Respect Time as a Core Resource

Developer commentary and industry analysis increasingly emphasize that player time is the scarcest resource in modern gaming. Long, grind-heavy quests can still exist, but they need to be:

• Optional, not blocking core progression.
• Transparent about requirements and expected time investment.
• Generous with partial progress—e.g., rewarding milestones instead of all-or-nothing completion.

In early WoW, grindy content sometimes served to slow players from hitting the original level cap too quickly. Today, with decades of content and alternative progression paths, that justification no longer holds as strongly.

3. Use Friction Intentionally, Not Accidentally

Some friction can be good: dangerous travel, meaningful decisions about what to carry, or challenging encounters create tension and stakes. The key is intent. The Stranglethorn page quest largely created accidental friction through clashing systems: bag space, RNG, travel distance, and item clutter all stacked in ways that weren’t tightly controlled.

Intentional friction tends to:

• Be clearly tied to a fantasy or narrative payoff.
• Offer alternative paths or ways to mitigate the pain (e.g., group play or crafting).
• Be constrained in duration and scope.

4. Learn Publicly from Old Mistakes

One of the reasons this quest still comes up in gaming conversations is that Kaplan and other developers have been remarkably open about where it went wrong. That transparency helps players understand design decisions and gives future developers a shared library of examples of what not to do.

In broader development culture, postmortems—both internal and public—are widely recognized as critical for improving software and game quality. The International Game Developers Association and conferences like GDC have long promoted postmortem talks as a way to share failures as well as successes.

Nostalgia, Re-Releases, and the Question of Authentic Pain

When World of Warcraft Classic launched, the question of whether to preserve the original, flawed quests became a hot topic. Many players wanted a pure recreation of the 2004–2006 experience, warts and all, including all the notorious grinds. Others argued for subtle quality-of-life changes.

The Stranglethorn page quest sits at the heart of this debate. Its presence raises questions like:

• Is authenticity to the original design more important than contemporary usability?
• Should historically bad design be preserved as part of the experience, or updated to reflect what we have learned?
• How do developers balance respect for nostalgia with responsibility to new players?

Blizzard’s approach in Classic and later in re-tuned seasons has generally erred on the side of preserving core structures while adjusting the most egregious pain points elsewhere. Even so, the existence of quests like this continues to spark discussion about how much suffering is “authentic” and how much is needless.

FAQs About WoW’s Infamous Page-Collecting Quest

Why do players still talk about this old WoW quest?

Players remember the quest because it combined high randomness, massive item collection, and limited inventory in a way that felt unnecessarily punishing. It became a shared cultural reference point and a symbol of early MMO excess.

Did Blizzard ever officially remove or heavily redesign it?

Over the years, Blizzard has made many adjustments to quest flows, rewards, and itemization, but the general structure of the page-collecting concept has remained recognizable. In modern versions and alternative seasonal modes, the overall leveling experience is smoother, which changes how the quest fits into progression.

What does Jeff Kaplan think about the quest now?

In later interviews and retrospectives, Kaplan has spoken bluntly about the quest as an example of his own early-career overconfidence—something he looks back on with a mix of embarrassment and fondness. His reflections are often cited in discussions about learning from design mistakes.

Are long, grindy quests always bad design?

Not necessarily. Lengthy or difficult quests can be compelling when they are clearly optional, communicate their demands upfront, and provide meaningful rewards or narrative payoffs. The problem arises when essential progression is locked behind poorly tuned or opaque grinds.

What can modern designers take away from this story?

Modern designers can use this example to remember that inventive ideas must be filtered through the lens of player experience. Respecting time, minimizing unintentional friction, and being willing to admit and iterate on mistakes are all critical lessons from this notorious quest.

Why This One Quest Still Matters

In isolation, the Stranglethorn page quest is just one piece of content in a colossal game. Yet its legacy endures because it represents a turning point in how designers and players think about what makes MMO content meaningful. It demonstrates how easy it is for ambition to slip into excess, and how candid self-critique from developers can turn a bad idea into a useful teaching tool.

As online games continue to evolve, with live-service titles constantly updating and refining their systems, stories like this offer a reminder: behind every legendary quest—good or bad—are human designers learning in public. The worst quest in the jungle may have frustrated millions, but it also helped push MMO design toward more thoughtful, player-focused experiences.