Swallow the Hero Whole | Art by Scott Chou
Call to Adventure
The story begins when I, a humble Magic development intern, was looking for my place in the world. Dave Guskin, who had then recently begun spearheading all of the branded play activities, was working on the Hero's Path campaign, and part of that was an idea for an in-store activity where you could fight a hydra. Many members of the Pit were interested in throwing out ideas, but as Theros was in development and "Huey" in design, many of them also didn't have time. And that is where I came in.
One of the advantages of being a new intern is that you have a lot more time on your hands than the other employees, and I took the opportunity to show the world what I could come up with. This was also a great test of my chops as a game designer, not just as a competitive Magic player.
I put together a prototype, taking my inspiration from Horde Magic, a variant designed by Peter Knudson, who was a former R&D intern. The idea was that instead of spawning wave after wave of Zombies, the Hydra would be wave after wave of heads, each with a different enchantment ability (this was an enchantment set after all). In this version, the goal of the game was to mill out the Hydra. The Hydra would start with three random heads in play, and then during its turn, it would flip the top card of its library and cast it. Some of these were small spells like deal 1 damage to each creature, while others were heads. When you killed a head, it would then mill from its library until you hit another head, then cast it. When the deck was empty, and you killed the last head, the Hydra was defeated. For this version, it meant you had to kill twelve heads.
Like any good prototype, this accomplished some of the goals of what we were looking for, but left a lot of room for improvement. The most notable problem was that because all of the heads had different effects, and only some did damage, the game felt a lot like a prison deck. Some of the designs, like Taxing Head above, were very weak in the late game, and utterly brutal in the early game. Some of this was fixed by changing the starting heads to a fixed line up, but it didn't solve the problems.
At the same time, Ryan Miller, former Duel Masters and Kaijudo lead designer, also put together his version of the game where the cards represented heads, and during each of the Hydra's turns, it would flip the top card of the Hydra's library. There were actual Magic creatures in there that it would cast. The other spells that were in the deck were Hydra spells. If the Hydra met the threshold in the top right for the number of heads, it would cast the spell. Otherwise, it would go into the Hydra's resource pile and act as a "head" to count toward further spells. While there were a lot of very good things in this design, it was a bit too complicated to work on auto-pilot, and required a human to make decisions for it, including attacking and blocking.
When I was eventually officially tasked with creating the real prototype for the game, I took elements from both my design and Ryan's, such as creating much more interesting spell effects and a few threshold effects that would only happen if the Hydra had a certain number of heads. After a few weeks of fiddling with the prototype, I turned it over to Ken Nagle, who was leading the design of the product.
Continuing Quality Improvements
The interplay between design and development is one of the elements that make us very strong as a department. Even though I had what appeared to be a workable game, it was far from as good as it could be. One of the reasons that we have both design and development teams is that we have found that handing our sets over to other people to work on leads to a higher quality product in the end. To that end, what the Hydra needed was someone to spend time coming from a different angle and trying out new things with the product. I had a set of goals that I wanted to accomplish, but so did Ken. He was able to really expand what I had pictured the Hydra was into something far more robust.
When the set came back from design, a lot had changed. Ken did a wonderful job at creating a number of fun and interesting individual designs for the heads and spells, including a few "whammy" spells for the Hydra, which he had found players enjoyed. He also added several rules, such as that Hydra head's abilities turned off when they were tapped, and that you could attack a Hydra head to tap it. This created more of a feeling like you were playing a real opponent that you could interact with instead of a program. It gave me a much better picture of the back and forth that I wanted the encounter to have.
I was given the position of the lead for a small team, meeting for about two hours a week, to develop the Hydra. My team was Erik Lauer, Magic's head developer, and Charles Rapkin, who works in our organized play department and would be one of the people responsible for messaging and getting stores to run the Hydra Game Day in the future.
The first development playtest showed many of the strengths, as well as the weaknesses, of the design at that point. One of Erik Lauer's biggest strengths as a developer is that he doesn't always follow the rules. While everything had been put into place with a clear goal of what the player was supposed to do, he immediately did the opposite—not killing the heads on purpose. While the tapping of heads gave the player a lot of strategic decisions, they often made the game too easy. A few quick creatures and the player would just "farm" the Hydra heads, turning off the ones that dealt damage and letting the ones that weren't doing much survive until the player had enough of a board presence to kill everything at the same time.
Another round of changes occurred—heads not tapping when attacked, heads "regenerating" by revealing the top two cards, and each untapped head dealing damage. If players wanted to, they could play cards to tap the heads to interact with them (and the Hero cards would give that opportunity), but it meant that they did need to do the "Hydra" thing and actually cut them off at some point.
Keeping It Simple
One of the items that I had been pushing for and working on from my earliest versions of the Hydra Challenge was a playmat that would contain all of the rules and set-up instructions for the Hydra. My reasoning was that a self-playing game intended for game stores only works if it doesn't require one human to teach it to someone else. There needed to be a way to make the rules as intuitive and easy as possible so a player could play it on his or her own. This did come with some baggage, though. While the upside was that a player didn't have to memorize the rules before beginning, it also meant that the rules needed to fit in a small space, which meant quickly pairing down the rules to the ones that really mattered.
It was during this time that the experience as a whole became far less complicated, but I think also was greatly strengthened as a result. The concept of "elite" and regular heads was added to make it clear how to start the game, as well as giving the game more variety. The elite heads took some of the more fun enchantment abilities and turned them into triggers. It also created more "You're Gonna Need a Bigger Boat" moments when a normal head died into a elite head.
In some of the feedback I have received, players have noted that the Hydra is weak against cards like Ratchet Bomb and Mind Grind. Some of the earliest versions of the rules attempted to solve all of these problems, but what I quickly learned was that the attempts to fix everything was just going to require a lot more work than was really worth it. In the earliest attempts to get this to work, I had tried to get every card imaginable to interact in a sensible way with the Hydra, but that just meant the players were constantly rereading the rules text to figure out which printed corner-case was put in place to deal with the current situation. Rather than addressing them one by one, we ended up cutting them down and implementing more generalized rules such as "just have fun." If a player came in with the dedicated goal to trounce the Hydra with a specialized deck, then that player was going to trounce it, and that was okay. It was far more important to keep the rules at a manageable level.
A Hero's Reward
One of the most useful resources that R&D has for testing our products comes not from R&D, but from one floor above: customer service. If you have ever called us to resolve a problem, chances are you spoke with a customer service representative. One of the perks of working in customer service is getting to come to the Pit on a regular basis to playtest upcoming sets or other products. There is a real risk that the people within R&D can get so into the minute details of game play or design that we miss the blatantly obvious things. Customer service playtesters are wonderful at giving us a preview of how people less familiar with the products will handle what we are producing.
Strike the Weak Spot | Art by Jason A. Engle
Something that we found during playtesting with customer service was that a lot of the Hydra battle was determined in the first few turns, when the player would take a lot of damage and would then just be racing the Hydra. Unless the deck he or she was playing had lifegain, it would feel more like a vice slowly crushing the player than an epic battle. The customer service representatives would often get frustrated as they would go to low life in the first few turns before managing to get a foothold in the game, only to get struck down by a card when the Hydra would live for a few more turns.
It got to the point where they often didn't like killing the heads, because they would often end up in a worst spot than when they knew how much they would be taking in the next turn. We attempted to make the opening turns of the game less brutal, but that often led to matchups where the Hydra posed no real threat. Getting the deck to operate at the exact level in the middle was looking impossible.
When talking with Ken Nagle, he mentioned that a number of video games have reward systems where you can regain health for completing tasks. From this conversation, an idea emerged—giving the player a reward when he or she killed one of the heads, the player would be up on the deal. This is where the hero's reward mechanic emerged. What we found right away was that we could increase the early game potency of the Hydra, and the player would often feel like things were hopeless—until he or she managed to kill a head or two. The player would begin to recover, only for the Hydra to get a lucky break and get the player close to death again. With this one mechanic, the back and forth between the player and the Hydra became a real thing, making the whole experience feel more like an interactive battle than just a clock to race.
That wasn't the final piece of development on the Hydra, but it was the final major change that got it into range of what it is today. A lot of work went into it by a lot of people that I haven't even mentioned here—from Dave Guskin's continuous championing of the project and getting a version of it to be sold on shelves, to creative for concepting and commissioning the artwork and designing the card backs, to our editing team for getting the rules to not only make sense but also work. Every product at Wizards goes through a tremendous number of hands, and all of them are required to make things work as well as they do.
The Hero's Journey
I am very proud of what we managed to accomplish with the Face the Hydra challenge. I feel we got a lot right in the design and development of the Face the Hydra Challenge Deck, but there is always room for improvement. I have heard a lot of very interesting rules suggestions from different people, as well as ideas on how to modify the challenge to fit different kinds of decks—from Limited to Commander. It was always my hope that, with this project, I could inspire people to try to make their own Challenge Decks or modify this one to better suit what they are looking to compete against.
I hope you all enjoyed this step on the Hero's Path, and I look forward to what we have to offer next year.
Until next time,