F. Discussion

 

Snake

The coding process of the first game, Snake, required continuous additions, testing, and revising. The game first consisted of a plot with set boundaries, a constantly moving snake formed by markers on the plot, and eggs, which are randomly generated markers on the plot. When the game was initially tested, it was observed that the snake moved too quickly to control, collisions between the snake with the eggs and the boundaries was not working properly, and the shape of the markers used to form the snake were not aesthetically pleasing. In order to better the product, the code was changed in order to slow the snake, change the markers from squares to circles in order to make a more organic shaped snake, and change the collision boundaries between the snake with the eggs and the plot boundaries so that the snake could eat the eggs easier and would not hit the boundaries so easily. After these problems were corrected, it was observed that more adjustments to the game could be performed in order to better the product. These adjustments included color change between eggs spawned, a title, a score system, and a main menu page. The change in the eggs was performed by randomly generating colors for each marker. The title of the game was added to the top of the plot, and the score system was created by assigning ten points per collision between the snake and the egg. This score was displayed on the plot. The main menu was created in order to display the instructions for the game and created a three second count down in order to allow players time to ready themselves for gameplay. The final adjustment made to the game was to add a continuously updated high score system. This was accomplished through the use of an excel sheet that allows players to enter their name along side their score. Theses scores are displayed after the game is over, which happens when the snake collides with itself or the plot boundaries.

 

 

Tron

The creation of the game Tron was very similar to that of Snake. The game consists of a plot with set boundaries and two continuously moving “bikes,” or red and blue lines. The bikes were formed by markers on the plot that are continuously generated in a specific pattern designated by keyboard commands. When first testing the game, it was discovered that grid points needed to be overlapped in order to create a more fluid movement of the bikes. Next, it was clear that the keyboard inputs would be different from that of Snake. These keyboard input commands required simultaneous inputs to account for the two players in the game. One player used the arrow keys while the other used letter keys on the opposite side of the keyboard. After further testing, it was clear that a system for detecting collisions needed creation, and would be separate from that of Snake because it would not only detect collisions between one bike and the other, but would detect which bike had collided and therefore which player had won that specific round. This lead to the creation of a score system so players could keep track of who was winning. This system would have a set limit of wins per player and would repeat itself once a single player had won three games. At this point, it was clear that the score system needed to be updated as it needed to account for ties in the score. A tie would occur due to head on collisions between players in which both players would be at fault for the end of that round. Later in testing, it was evident that a “play again?” feature needed to be added in order to allow players to continue playing after one player had one three rounds. Finally, a main tune needed to be added in order to allow players to read the rules and instructions for playing the game before beginning gameplay.