top of page

MaxHorsePower

Team Size: 5

OverView

MaxHorsePower is a game where the player is trying to beat other AI using their weapon and dodging traps to get to first place. The overall process of making this game was in one month where we had to rapid prototype and see if this idea will work. We wanted to give the player an experience where that raced AI but also had to worry about getting shot by them or hitting traps. This ended up getting scraped since we had trouble focusing either on combat or racing. Communicating was a big part of this project and which helped us grow as a team and further our adventures together to create something that we are all proud of.

Responsibilities:

​

  • Made traps that did random amount of damage and takes away coins

    • There are 3 different tiers​

  • Made enemy health bar that displays above them 

​

​

What went right:

1. Physical Meetings

Even though we were all campus students we still met up after school and worked on the project and went over things that had to get done for the week. Since this was a rapid prototype game to prove our prototyping skills we had to hunker down and get work done by any means necessary which even meant staying after school and working on it with each other. These meetings helped all of us by getting to understand each other and each other work ethic. It also helped us in if anyone needed help or had a question we were right there to help each other. There were times where someone didn't understand how something worked that they made and we were able to sit down and explain step by step with little to no confusion at all. These meetings also made it easy to sit down and have stand up meetings to help other people know where they stand in terms of their work.

​

2. Communication
Since this was the first time working with each other on a big project we kind of expected communication to be a bit of a problem for a bit but I was wrong. Communication for this project was really good and was little to no miscommunication to what was being done or what was done. This kind of ties in with the physical meetings but with us being at home as well we were able to communicate well with each other through Discord. Most of us were on most of the time so we would hop in a call with each other to discuss what had to be done for this week.
 
What went wrong:

1. Learning new engine
Learning a new engine was a challenge since during our time in school we learned Unreal 4 once. While learning the engine we had no idea the syntax of everything so we ran into some bumps on how things work. We as a team had to come together and do research on everything that we were doing to make sure we fully understood what exactly what each thing did. We would try to implement things that we didn't know and would end up losing time. This project ended up getting scrapped because we could,t get the feel of the game that we wanted the player to feel since we find,t know how C++ worked and haven't fully understood the basics of the engine yet. As the month we spent on this project we did end up learning the engine a little more but still had a lot to learn for the upcoming months ahead
​

​

​

bottom of page