F. Discussion

Buckeye Trail was first planned out using a flow chart of each scenario that the game would contain. There were 8 tasks that were split up for the iterative coders (Brian and Mallory)  to code the individual strains. The individual strains consisted of if statements that were dependent on user inputs. These strains were then given to the code compiler (Hannah) who created chained if statements, where correct choices would lead to a new embedded if statement, and incorrect statements would lead to the end of the initial if statement. Finally, the audio and visuals were added by the person in charge of them (Caleb), in order to enhance the general effect of the game. We then decided to add a while loop was added to act as a halfway checkpoint for the game. Welcome statements were included with a prompt for users to input their name in order to personalize a gamer’s experience. Some obstacles came up when we compiled the individual strains of code together. We had to be careful to ensure that each if statement was embedded in the others correctly and in the correct order. It was also difficult to figure out how to create the checkpoint, but we eventually figured out how to implement it through the use of a while loop.

During the game’s testing everything went smoothly. The participant was able to follow directions and was successful in finding Brutus and winning the game. The checkpoint was tested and worked successfully. The music that was supposed to play at the end did not, but this was due to a lack of speakers on the computer that was used to play the game.