Dev Log #5

While some use a more traditional predictive process, most embrace the adaptive methods of iteration that allow game designers to design and refine the game through successive iterative loops. - "The Iterative Game Design Process" Chapter 5. Today we played a game called Sushi Go. This game was a card game that involved a lot of repetition, strategy, and luck. I did not understand that much at all at first but after a few turns of playing with my class mates it started to finally make more sense. The objective of the game was to match cards with their respective matching cards, and gain as many points as you can. You place a card down each turn and hand your deck to the person next to you. The cycle then continues until you all run out of cards. 

The main thing to keep in mind is that all that’s needed is a kernel of an idea. - "The Iterative Game Design Process" Chapter 5. At first when we were playing this game I almost had no idea what the objective was. But I knew for sure that you had to match cards. Matching the cards either granted you a win or granted you points that you needed to add in order to win. I understood that you needed to switch decks with the person next to you but I did not know why until I started playing the game. Once we started playing for a little bit, everything just started to click. 

Often, what seems like a great idea that makes sense in a prototype falls apart when players get ahold of it. - "The Iterative Game Design Process" Chapter 5. At first I had a completely different idea on how Sushi Go was supposed to be played. I thought all you had to do was match cards and then you win the game. So I did as such in the beginning but I wasn't doing so good because I didn't realize that that is not actually the whole premise. There were also some things I did that I thought were rules, such as placing two of the same cards down because they matched. I then realized you can only place one card down at a time.