F. Discussion

High/Low/Sevens

  1. Game Testing
    • Paul Bowman tested this program on 11/15/18. He said that he enjoyed the graphic and thought that the act of betting helped to increase the overall enjoyment. No negative remarks.
  2. Progression
    • This game was created in about 2 hours. The initial version was attempted without functions, however, the simple game began to become complicated very quickly.  Functions were then added and the programming became much more simple. After one hour the game was completed and the rest of the time was spent on debugging. The following week in class the dice graphic was added to make the game more enjoyable and visually stimulating.
  3. Obstacles
    • The only obstacle was debugging. Many of the errors resulted in either changing some variables and forgetting to change all of them or misspelling variable names when calling functions. Overall this program had very little obstacles as it is a very simple game.

War

  1. Game Testing
    • Each person in our group tested the game to make sure it would run properly.  The game worked just as expected.
  2. Progression
    • The game was created in about 4 hours.  The code in our initial version was very messy and we only used one function; we found it very difficult trying to get the game to work in that one function so we decided to scratch it and start over but instead make a few functions for the purposes we needed.  After about 3 hours the game was completed but there was some debugging to be done with the graphics of the game.  It took about an hour to figure out and the final product works as expected and is enjoyable to play.
  3. Obstacles
    • The biggest obstacle for us in creating this game was actually figuring out how to get the graphic of each player’s deck of cards to be equal to the actual card’s they had in their respective deck array.  It turned out, we were calling the wrong function so it gave the wrong output each time.  Another obstacle faced in the creation of this game was figuring out what we needed to get done and how those could be broken down into functions.  We overcame this obstacle through help from our pseudo-code.

 

Blackjack

  1. Game Testing
    • We tested the game both within our group and on Paul Bowman.  The game was reported to be exciting and stimulating.  It worked exactly as planned.
  2. Progression
    •  The current version of the game was created in roughly one hour.  But at the start, the game started as a different version of blackjack.  Functions were not commonly used in this version and it became overwhelming and extremely confusing very fast.  Therefore, a new MATLAB script was created and utilized many functions.  Many of the ideas from the games transferred over but it was much more simplified in the second version and much easier to create.
  3. Obstacles
    • The main obstacle was the confusion from the first version.  There were hundreds of lines of if/else statements and it became too confusing and almost unworkable.  We overcame this obstacle by creating a new game that utilized more functions and this helped simplify the process