Conclusions:
Overall, the entire design and implementation process went relatively well for our group. We were able to split up the work easily and every teammate adhered to our group deadlines and expectations. One issue that we did encounter was that it was difficult to combine all of the individual parts that were written by each group member. Some of the variables and position values were set differently and it was tedious to get each part to work together. However, through the challenges we faced with implementing different code segments, we learned the importance and utility that comes with defining constants and using public member functions in a class.
Recommendations:
Ideally for our game, we could implement more TA battles along with changing some of the code to make the game run smoother on the Proteus Simulator. If we had more time to work on Rock, Pokémon, Scissors, we would like to implement a few more features. We wanted to implement a feature where the user could type in their name after beating the final boss, and we could then have a statistics page off of the main menu showing any specific user’s name, wins, and losses as a sort of long standing “leaderboard”. We would also like to add a feature where, prior to battling a TA, the TA character would move up to the user’s character and display text before the screen is swapped to the battle layout. The final feature that we had discussed adding would be sound effects, but we would be unable to because of the Proteus Simulator limitations – our favorite feature would have been the implementation of different background music and battle sound effects.
References:
For our project, we did not use any references to assist us in crafting the code. However, we used the name and ideas for our game concept from the following entities:
- Nintendo: The Pokémon Company
- Game Freak
- Textcraft.net, available online at: textcraft.net/style/Textcraft/pokemon