Dev Log #7

"Playtesting lets us see what’s working and what’s not".  - O'Reilly Macklin and Sharp, Chapter 11.  Today in class, my group and I had a card game ready to play and present. However we thought of ways we could make the game more exciting. In the first prototype we had, the game was cooperative between all of the players that are playing. The prototype did work out very well, but it didn't feel very fulfilling.  Every time we played, we always won together. So we decided to switch it up and make it more competitive. We decided to add two teams instead of one and make it a race. The objective of the game is to use all of your cards. You can add and subtract numbers but you cannot pass a certain number. But with the second prototype we had, we decided to make it competitive and it worked out much better than the first. 

"As a designer, anytime a question arises about the game’s design, a playtest should help find a suitable answer." - O'Reilly Macklin and Sharp, Chapter 11. When we were first designing our game, there were of course some flaws to it. There were questions on how we were supposed to win the game and how this can be meaningful to win since we were all playing together as a team. We played multiple games and added a new rule and mechanic to each game we played to see if it can better than before. 

"In fact, certain prototypes work best with certain play testers." - O'Reilly Macklin and Sharp, Chapter 11. As we were prototyping our card game, I noticed that there were members in the group that came up with more ideas than the others. This probably is due to those certain players having more knowledge in card games. These members have probably played a lot more card games than others and then took inspirations from those other games and implemented them into our game. If i were to be prototyping a video game first person shooter for example, I would probably have a lot of ideas to implement into the game since I have played a lot of fps games in my life.