Throughout the process of making this game there were things that went well with some challenges along the way. Our team came together with a strong plan that created a solid path to follow. Things like working diligently, assigning roles, and working together to solve problems all contributed to moving along the process. Some aspects such as creating fun backgrounds and editing components of the main menu went particularly smooth. Going further into the process helped us to better understand how to move forward. After completing level one it was clear that we were on the road to a successful game.
Some problems were encountered during the process as well. About halfway through we had checked the requirements and discovered that the way we were working now would not include all required elements. However, with some discussion on how to move forward we planned on ways to include all the components needed. Some things had to be compromised during development to help things work better such as levels being shorter or less complicated than anticipated. Other problems seemed small but were much harder to pinpoint and fix within a nearly complete code. For example, attempting to make objects move at the same time or fixing a screen that displays incorrect data. However, learning to work in an organized way and developing a solid understanding of the program allowed us to work through each problem one by one.
If there were to be future development of Engineering Dash, we would have added more obstacles or made each level longer and more complex. Also, timed jumps to go with background music is a large part of what makes Geometry Dash, the original game, so fun. If given more time we would add something similar. Finally, a character select feature to choose what the square looks like would also be interesting to add.
FEHSD.h | FEH Proteus Guide (osu.edu)
Guidance from TAs and Course Instructor