Replayability

Author: Cameron Taylor

As part of the final build the game needed replayability without restarting the program. I solely chose to solve this and the first thing was to allow the player to go back to main menu and restart the game from the main menu. The challenges I ran into was the gamestate that the main system "thought" it was on. I used the gamestate and sent messaged to intermediary to know when they could use the exit button and what to do. The other issue was level constructor was never setup to handle going back to the main menu or reloading the start floor. So when attempting to throw them back and forth I ran into plenty of issues with doors going invisible or just completely breaking. The enemies also started cloning themselves which is obviously not great for gameplay.

To fix the button issue I needed to add new states to the build so that I could further figure out where we are in the program and started storing the previous state. For the next issue I needed to add some functions that would handle making the main menu and first floor instead of having them inside init. This wasn't too difficult, but I needed to handle what functions were then being called from intermediary which was slightly annoying in the beginning. Overall the game is now super replayable with death, pressing exit, ect. The only way to close the game now is by pressing exit and then walking to the exit door.




Comments

Post a Comment

Popular posts from this blog

Adding assets to every enemy -- Owen Meyers

Image
      As with every game, it is very important to have assets to denote which enemy is which. Being able to tell at a glance what enemy you are encountering before receiving a face full of buckshot is incredibly important. The issue for Project [REDACTED] is that we didn't have any artists working full time to deliver assets for the enemies. Thus, it fell upon me, the designer of the asset pipeline, to acquire assets for every enemy. This led to having to fix models and integrate animations, with each problem being subtly different.     Take, for example, the shotgunner model. His original model was designed for an OpenGL renderer, and was flipped 180 degrees for that very reason. In addition to this, he was also placed halfway in the ground, likely due to something required for that game's collision to function. Fixing this model to function for our renderer required that it be re-rigged and most of the animations acquired from Mixamo. With the help of Kris, and several hours
Read more

Sphere to AABB collision

       I had a problem today when trying to detect sphere to AABB collision. For some reason the collision check that I made was never turning true even though I could clearly see the sphere hitting the AABB. This was a big problem as we needed this collision to detect whether any entities are hitting walls.     I discovered that the problem with this bug was that I was improperly getting the closest point in the AABB to the sphere. The way I fixed this problem this problem was by getting the max vertex that the circle center could be and using that to get the closest point on the AABB to then determine the minimum vertex between the sphere's max vertex and the max of the AABB.  Once I found this point, I could properly compare the distance of that point to the center of the sphere. This solution will allow detection between walls and any sphere collider such as the player collider, and enemy collider. This is very important to make sure they both stay within the level bounds.
Read more