G. Conclusions and Recommendations

After our game was put together completely and tested, we were pretty happy with our final result. The game met all the expectations we worked towards including multiple steps, a check point, visuals and audio. The code without the comments throughout was not too long. At the end of writing the code it is safe to say any type of adventure game consists of a bunch of “if” statements but the programmer can add any other form of coding depending on what they want to implement into their game. I would recommend completing the code by splitting it up among group members by the steps and making sure each persons steps work separately. This way if an error were to occur, you can just edit the portion of where it occurs. Then in the end, adding them to one single document and making them flow correctly.  Another recommendation is to choose one computer to have the images and audio files saved onto it and designate it as the testing computer to make sure everything loads properly. If we had more time or went full scale, we would’ve used the “tic-toc” function to time how long it took to complete the entire adventure. We also would’ve added many more steps and maybe even mini-games within the tasks provided. I would also look for a better way to display pictures as the game was played rather then opening up a new window each time.