Put simply, a power curve is the average value a player gets in exchange for spending a given amount of resources. It’s most often used when discussing card games like Magic the Gathering, Yu-Gi-Oh!, Gwent, and of course Hearthstone, but it is still applicable to most games. As a general rule, the more resources you spend the more value you should get, and this relationship tends to be linear.
Read moreDesign Tips: Tell A Story
Back in February I attended the 2018 Learning and the Brain Conference in San Francisco. I went to the conference because I thought it sounded interesting and I was hoping I could learn something that I could apply to game design. Unfortunately, I quickly learned that many of the sessions were geared towards traditional educators, so I was worried that there wasn’t going to be much I could take away. But then I noticed that several sessions focused on storytelling and I found that the lessons I learned from them had broad applications beyond education. So now I’d like to take the time to share with you 5 things I learned about storytelling that are applicable to game design.
Why does this matter? Put simply, it’s because we crave stories. Nothing holds our attention and engagement quite as effectively as a good story. So why not increase the immersion and enjoyment of our games by framing them around stories? And even if your game lacks a traditional story structure, there is still the story of your players playing your game.
1) Stories are fundamentally about solving a problem
Broadly speaking, stories tend to be structured like this:
The protagonist has a problem.
The protagonist tries to solve the problem.
The protagonist ultimately solves the problem, or they fail to solve the problem.
This is shockingly similar to a game, isn’t it? Here’s a typical structure for a game:
The player(s) have a goal.
The player(s) attempt to achieve that goal.
Ultimately the player(s) accomplish that goal and win, or they don’t and lose.
So even in games that lack a traditional story (i.e. Tetris, Chess, Go Fish, etc.), there always exists a story centered around the “play” experience of your players.
2) Plots are overrated
When people think about stories, they think it’s all about the plot. But this isn’t really the case. Plot is just the sequence of events that occur in the story. Without giving those events meaning and context they aren’t very compelling. So instead of focusing on the plot, focus your stories on goals. Stories aren’t about going from A to B to C to D, it’s about why we want to go from A to D.
3) The hero needs to struggle
Tell me what’s missing in this story:
“There once was a knight who wanted to save a princess. So he went to the tower where she was locked away to rescue her. But there was a dragon standing in front of the tower. So the knight walked into the tower and saved the princess. The end.”
Okay, so obviously there’s a lot missing in this story. But the main thing missing is a struggle. When our hero confronts the dragon, the main obstacle in the way of achieving his goal, he immediately overcomes it. How is that interesting? If the obstacle doesn’t do anything to prevent the hero’s progress towards the goal, it’s not really an obstacle. What if the dragon posed a real threat or challenge to him? What if instead when he tried to get past the dragon he failed and had to try again? By having the hero struggle and fail against an obstacle it makes their story more compelling. This same concept applies to games. If you confront an enemy and immediately defeat it, was it really ever in your way? This doesn’t mean you should make all your enemies impossible to defeat, but they should at least pose some challenge to the player.
4) Every character needs a goal
The hero isn’t the only character that needs a goal. In fact, every character needs a goal. Using our above story, we gave the knight a goal to save the princess. But what about the princess and the dragon? Why is the princess in the tower? Does the princess even want to be saved? Why is the dragon at the tower? Does the dragon want to keep the princess locked in the tower? Does the dragon want to eat the princess? Does the dragon want to help free the princess? By knowing each character’s individual goals, we can see how they align or conflict with one another to create tension. This same concept applies to games. Whenever a player interacts with a character in your game (i.e. an enemy, an ally, another player, etc.), that character should have a goal. That goal can hinder, complement, or be unrelated to the player’s goal. Use those goals as a guide for how they’ll interact with each other.
5) The hero needs to change
Heroes aren’t interesting if they always stay the same. By the end of the story the hero shouldn’t be the same as how they were at the beginning. Instead, they should have changed based on the events of the story. The players should change as well. The player should have learned something from playing the game, even if it was just how to play it better. If your player didn’t learn anything, they probably won’t want to play it again.
So those were the 5 main things I learned about storytelling. Hopefully you learned something from them as well. Want to make your own stories but don’t know how to start? Here’s a simple template you can use to get you started. Good luck and happy writing!
Once upon a time, there was _______.
They wanted to _______ because _______.
But _______. So, ______. (repeat as needed)
Until finally, _______.
Want to learn more about storytelling? Check out Jonathan Gottschall, Kendall Haven, and Jason Ohler, as their presentations directly inspired this blog post.
Design Tips: The Batting Cage
So I'm not a baseball player, but I do perform some great work in the batting cage. It's a word that I made up on the spot that accidentally stuck even though I'm 100% sure there's a better metaphor somehere.
The Batting Cage
Definition
Batting Cage Idea: An idea that is not meant to be a proposed solution, but rather meant to inform the brainstorm session in case there's a good idea that can come from it.
(Why not just brainstorm? Why the separate term?)
To be totally transparent about this, I think it's mostly psychological - I feel that a lot of the time people are scared of saying their idea because it's obviously not going to be the solution needed, and people are just going to judge them for saying a 'waste of time' proposal. The "batting cage" disclaimer lets your idea be heard for the sake of inspiration instead of for the sake of evaluation.
Example
"Okay, so what other levels could we make for our protagonist 'MatchEars'? Other than avoiding methane houses?"
"More fuse lighting? A lamp level?"
"I feel like it'll get old if we do that again, and the paper lamp level sounds already a lot like the hot air balloon level"
"OK, batting cage: underwater level. Or something with water, I feel a nug there."
"Oh, what about a level where it periodically rains, and he needs to hide underneath awnings?"
This isn't to say that MatchEars should ever be made into a game, or that any of the above ideas are good. But this should hopefully exemplify how a batting cage idea can be useful to conversation when with people who can appropriately spring from it.
Benefits
1) The main reason you do this is to inspire others. If someone else had a half-idea but were missing a piece, now you'll maybe indirectly deliver that piece!
2) If you know there's something good in the idea, but you're not sure how it can be shaped, it shifts the conversation away from why it's bad (because what a waste of time -- you already know it's bad) and towards how it can maybe be good.
3) Sometimes it actually is a great solution, and your doubts were just because of how buckwild an idea it was. The "batting cage" disclaimer gives you the courage to say your ideas, and it happens more often than you'd think that a batting cage idea is actually the perfect solution as-is.
Drawbacks
1) If people don't know what "batting cage" means, then they'll just critique your idea and not realize that you weren't doing a proposal in the first place. It ends up wasting time.
2) It gets easy to just slam "batting cage" in front of all your ideas as a means to protect yourself from critique -- don't do that! It'll lose its 'power' (so to speak) if you aren't honest with yourself when you're actually giving a proposal.
3) At some point, people need to start synthesizing all these ideas into real proposals. A team's workflow is best when there's a good group of people who are actually capable of drawing inspiration from what you're saying.
Give it a shot!