Wow. This is happening! I am getting ready for my first designer convention – Protospiel-Milwaukee. This weekend I will be taking my game, Scoville, to have it played by other designers and see whether or not it actually has any potential.
Protospiel is a board game designer convention where designers bring games that are in work. Then you can have your game played by other designers and you can return the favor.
One of the best parts about this weekend’s convention is that I will get to meet a ton of great people in the board game industry. There are several designers that I follow on Twitter that I will have the privilege of meeting. What is especially nice about that is that those guys know what they’re talking about. Several of them have had games published. You can probably find them in your local game store right now. I won’t name any names so that I don’t exclude anyone, but I am definitely excited about meeting the designers face to face.
What do I have to offer?
I will be bringing Scoville. Scoville is a game about cross breeding peppers. As a player you take on the role of someone who has been hired by the town of Scoville to fulfill their recipes for the hottest peppers. To do that each round consists of an auction phase, planting phase, harvesting phase, and fulfillment phase. But the real highlight of the game is how the planting and harvesting works.
The main mechanic of the field map is what I think has the most potential in this game. Each round players have to plant one pepper in the fields. Players can plant a second pepper for $6 if they want. Over the course of the game the fields get filled in. During the harvest phase players will move their pawn up to three spots. Each spot is a location between two fields. If those two fields have peppers on them, then that player will receive whichever pepper(s) is cross-bred from the two existing peppers. For example, if you move your pawn between a field with a red pepper and a field with a yellow pepper, then the cross-breeding result would get you an orange pepper.
Part of the goal with Scoville was to create a game where players start with basic, or primary, resources (red, yellow, and blue peppers). Those basic resources can then be used to cross-breed better, or secondary, resources (green, orange, purple). Those secondary resources can then be used to cross-breed even better peppers (black and white). And finally if players can plant a black pepper next to a white pepper, the resulting cross-breed would be a gold pepper. I really enjoy the flow of this game where players are working toward getting the best resources while at the same time hesitating to plant the peppers that could give those resources since the fields are shared by all players.
Here is a guidesheet image from a previous version of the game:
I have updated guides with the latest game revision that I will be using this weekend. It is mostly the same as what is shown.
And there is already some buzz about the game. Not really. But I did fill out the game preview form on Cartrunk Entertainment’s Unpub.net website. You can read my preview for the game there: Unpub Preview – Scoville. Thanks go to John Moller for posting that!
Preparation Left To Do:
I still have some things that I need to get put together before I attend. Here’s my to-do list before the convention:
- Write the rules – Yep. I guess I’m procrastinating here. But it is surprisingly difficult to put all your thoughts into rules on paper. And it can be tricky to make the most applicable images to add clarity to those rules.
- Finish putting together a second copy of the game. In the event of a publisher wanting to take a copy with them I’d like to have one available. In the 99.99% probability that no publisher wants a copy, then I want a second copy available to leave with a fine gentlemen for inclusion in the Prototype Penpal Program.
- Pack my bags.
I’ll probably have a long night tonight working on the rules. But if I get them done today it will give me time to revise them tomorrow. A second copy of the game is almost complete. I have everything printed. I just need to stick it to card stock and make some player shields.
Making the Most of the Convention
So since this is my first designer convention I want it to be the best it can be. That means I want to make great connections and I’d like to receive excellent feedback for Scoville so I can improve the game. Last week I posted a thread on BoardGameGeek: How to Make the Most out of a Designer Convention. I got some excellent replies. One common piece of advice from the thread and other sources is to have a good open attitude. This applies to receiving feedback for my own game and also to giving feedback for other’s games.
Another good set of advice came on Twitter today from @BrettSpiel. You can read his ten tips on Cardboard Edison: Tips for Protospiel.
So I think I am all set. I’ve got my game. I’ve got a good attitude. I’ve got a notebook for documenting all the awesome suggestions I’ll be receiving. And I’ve got a good friend attending with me as a play tester. It’s gonna be an awesome weekend!
Origins of Dam It
Two summers ago I came up with a goofy game design. Last week I wrote about the game being rejected, and what I learned from that. I called the game “Dam It!” The goal of the game is to build a dam across the river before any of the other beavers build their dam. Since the game was recently rejected by a publisher it is now back in my hands. So today I bring you my “designer diary” about the game from concept to its current state.
When I came up with the game I had the idea that it would be really cool to play a card game where you stacked transparent cards so that an image was built up after a few cards were piled on. This fit with a dam theme since you could stack cards to complete a dam (logs, sticks, mud, etc.). The problem with that is that when using transparent cards you can always tell what the other players are holding unless the outlines are the same image. And if the outlines are the same, then there’s no point in stacking them. The only way to make transparent cards work is to have separate decks; one for playing and one for building. So I threw the transparent card idea out right away. But for some reason I still made a game about building dams.
So I came up with the idea to build a dam using Big Logs, Twig Filler, and Mud. Oh, you can also hire helpful beavers to build more efficiently. And you can damage your opponents dams by sending stones or weeds down the river.
Now I had a bunch of cards to make and I had what I thought was a good system for how those cards would be used. Big Logs, Twig Filler, and Mud would be the building materials. Weeds and Stone would be damage cards. And Angry Beavers, Eager Beavers, Mildly Eager Beavers, and Busy Beavers would be the hired help.
The First Play Test
I made a board for up to six players. I printed and cut out about 160 cards. And I got my friends to try it out at a board game day. Here is a hastily made reproduction of what the original board looked like:
On your turn you would draw two cards and then play any or all cards that you wanted to play. When you played sets of cards onto your dam you would remove the appropriate number of cubes from that dam section. When your turn was done you would draw back to five cards.
The first play did not work so well. We were able to play the game, but it was like driving a Yugo down the road with two flat tires. The first problem was that the game took forever. Early on players would have to gather a set of 4 Big Log cards just to get a dam section started. Those Big Log cards each had a percentage on them. When the set of four was played, the percentages were added together and that is how much the flow in that dam section would go down. But players would have to get sets of four for Big Logs, Twig Filler, and Mud. And they would have to do that for each of the 5 dam sections. Changes ensued!
Making it (Marginally) Better
To make the game better and to speed the game up I made the following changes:
- Decrease from 5 dam sections to 4.
- Remove the percentages of the flow decrease on the cards and standardize each set. (i.e., all Big Log sets would be worth a 30% flow decrease).
- Increase the number of cards in a player’s hand from 5 to 7. This would allow for better probability of getting the required building sets.
So with those changes the game played better. But there were still problems. The downtime was too great. The interaction was minimal. And the greatest problem was that the game depended too heavily on getting the right cards. Often there would be one or two players who would just never draw the Big Log cards. And you can’t start building until you get them. So they just sat there at the table unable to do anything fun in the game. That’s boring. So I made more changes.
One of the best ways to illustrate the changes in the game is to show the evolution of the Big Log cards. Note: the log artwork on these cards is from Microsoft (here) and another source that I must not have documented. For future prototypes I plan on using only original artwork or artwork from sites like Game Icons.
In that image you can get an idea of the evolution of the game overall. One of the biggest changes was going from removing blue cubes which represented flow to adding brown cubes which represent the actual dam you are building. Another key change was to allow the Big Log cards to either be used individually or two at a time. Using them individually could help get you started faster. Using two at a time could help you build one section more quickly. But…
People Still Weren’t Having Fun
So during that playtest the night before potentially pitching to a publisher at GenCon one friend of mine pointed out that the game just wasn’t very fun. That’s a HUGE problem. The whole idea of designing board games is to create an environment where the players will be having fun. The comments were the same: minimal interaction, runaway leader, never getting the cards I want. So I made a change that added two new beavers: Sneaky and Grumpy.
The idea of the Grumpy beaver is to increase the interaction between players. Previously the weeds and stone could only be sent downstream. In the late game situations this basically meant you could only attack the player to your left. But if the player to your right is really close to winning, you’d probably rather attack them. So the grumpy beaver, when paired with stone or weeds, allows you to attack any other player, not just downstream.
The idea of the Sneaky beaver is to help prevent a runaway winner. When a sneaky beaver is played one player is attacked. The person playing the Sneaky beaver will remove three cubes from one dam section of the player being attacked. Those cubes are then given to other players and placed on three separate dam sections. This helped with the runaway leader problem.
So I had solved two major problems with the game through one revision. But was it any fun? Just the other night at our board game night the person who had never enjoyed Dam It mentioned that it was never any fun until these two beavers were added. That was music to my ears. So I had converted the hater. And I was now confident enough to send this game off to a publisher.
Yep… the game was rejected. You can read about that in last week’s post: Lessons Learned From Rejection. However, I received some excellent feedback on how to improve the game. The two pieces of feedback I found most helpful were:
- Use the cubes for more than just visual notation of the current state of your dam. For example, be able to spend cubes for a special action.
- Mitigate the luck of the draw aspect by having several cards face up to draw from, a la Ticket to Ride.
Both of these will increase the options for your turn, and give a player more to think about. Good stuff!
One of the things that I thought was really important was the art of the prototype. I should mention that this was before I followed a ton of great people on Twitter, who know what they’re talking about. I thought that the art had to be really good. I didn’t want thin paper cards with minimal art and sketches and notes. I wanted a product that looked complete. I thought this was important for the publisher. Why did I think that? Well, it seems like an obvious thing because it’s the idea of making a good “first impression.”
This was a problem for me as a designer because I spent way too much time working on the art (in The Gimp) when I could have been play testing or designing other games. While I enjoyed working on the art, it just wasn’t important. What if the publisher chose to publish the game, but also chose to re-theme it? Then all that time would have been potentially wasted unless.
Another thing that I would have done differently is to send the game off for blind play-testing. One great program for this is Grant Rodiek’s Prototype Penpal Program. I think blind play-testing is critical so that you can test not only the game, but also the clarity of the rules, from people who are not biased towards you. I plan on utilizing the Prototype Penpal Program after attending Protospiel-Milwaukee in March.
In hindsight there are plenty of things to change about the process I went through with Dam It. I’ve learned tons but only because I made the mistakes that I made. Sometimes it’s better to learn by doing, even if the doing is filled with mistakes.
What’s in Store for Dam It?
I will not currently pursue this game any longer. It is an appropriate time to shelve the project. I am currently heavily testing and revising my game, Scoville, so that it will be ready for demonstration and play-testing at Protospiel-Milwaukee in early March. Since Scoville has more potential than Dam It it means the beavers will have to take a back seat. I also have other game designs that I feel are more intriguing than Dam It that are not quite at the prototype phase yet.
If I were to pursue major revisions for Dam It I would start with play-testing the face up draw cards. That seems an obvious improvement to the game. I would also brainstorm the potential other uses for the cubes. I have added the face up draw to the rules, which should hopefully be up on BGG in the near future. If you want a copy of the rules, just let me know on Twitter.
Dam It has been a fun first game to work through the whole process of invent – prototype – play test – submit. I learned a ton and had a lot of fun. I think Scoville has definitely benefited from my experiences with Dam It! Want to find out? Come try it at Protospiel-Milwaukee!