CAGD 377 - Slippin Away Sprint #4

 For the Sprint, there were various things that I wanted to tackle, mostly fixing bugs and adding some basic animations. During Sprint Kickoff, I was tasked with polishing some of the previously implemented mechanics. My first approach to handling the problem was to set a priority for every bug and start working from there. After having the feedback from our playtesters, I had a general idea of how to fix some of the core bugs. 


First off, It was polishing the character controller so that the player wouldn’t get stuck as easily; previously, if the player were in a corner, they would get soft-blocked. After looking at the code, it was a problem in the main logic of the character controller, so I had to change various aspects of the character controller; first, I had to make it so that the controller is stuck and independent and not depending on the box collider attached. Using my previously implemented custom collision detection system, I could check when the player hit a corner without using the Sphere collider attached to the game object.


Using the custom collision detection system, I could also get the direction in which the character collided and snap it to a degree. So, using the data from the collision detection, the character will get a rotation angle, and the model will be rotated depending on the surface the player landed on.



After this, I was able to implement something I wanted to implement into the game, which was adding some basic character animations so that the gameplay would feel smoother and Guppy would feel more like a living being. I started doing the idle animation in which if the guppy is in the ground, it will go back to its original form and stretch; it will also have a slight movement left and right. I also added the Jump Animation in which the guppy will perform a downwards and upwards animation so Guppy can feel like it's jumping, and there is some pre-stretching instead of just jumping. Thankfully, because of the way the character controller was set up, I did not face any problems while developing and implementing these animations.




After this, one of the most complicated things to do during this sprint was developing the Star System, which is meant to display how many stars you got at the end of a level. This also meant that we needed an objective system. Unfortunately, another objective system was previously implemented in the game. However, working with the Star System wasn’t as modular, so I had to make a new one from scratch. Something that I had in mind while developing the objective system was so that the designer process would be easier by using scriptable objects and choosing the objective type. For this sprint, the designer only wanted two objective types: timed objectives and reaching the end. Thankfully, since we were already keeping track of the game in the Race Manager, it was easy to use that playtime to check for timed objectives. The system was also made so that if the designer wanted to ask for more objective types in the future, they could be easily added to the game. After the objective system was done, I had to work on the Star System, which would check the state of the level objectives and display them once the player ended, either by dying or reaching the end.



Finally, during this sprint, I had to make an Android build, which faced some challenges due to the changed Android bundle version. However, after some debugging and talking with the producer, I was able to figure out the problem, and we were able to push the build to the Google Play store.


Overall, this sprint was great, and we made a lot of progress. My team has been keeping up with all their work, allowing the whole team to be on track to release this game on the programmed due date. During this sprint, I was also able to work on and understand more about the Unity animation system.

Comments

Post a Comment

Popular posts from this blog

CAGD 373 - Pirate Game Assets Final

Image
  Game Walkthrough:      The goal of this project was to recreate a location from Sea Of Thieves. My team decided to work on an outpost with a stationary sloop and a tavern. We needed to make the mountains similar and add many assets that would be interesting for the player to look at, like the barrels and the lamposts. Also, we needed some interactivity, like cannon shooting and quests. My role on this project was the programmer in charge of implementing all the systems regarding the gameplay. So I managed to make the player movement, interaction with barrels, shootable cannons, a quest system, the final battle, money systems, a high score leaderboard table, and many other small systems within the scene. I also tackled Unity-related tasks like generating a new water shader and sculpting the terrain. One of the problems I faced was dealing with the inventory system since that took a whole sprint on its own, and I did not have any prior experience designing one. I tac...
Read more

CAGD 470 - Locked in Sprint #1

Image
  In CAGD 470 (Video Game Production), I was recruited into a group that wanted to make a first-person horror game in which a player is in a laboratory and trying to escape. At the same time, some monsters roam around, making the player’s journey difficult. The game will have various rooms and puzzles that will challenge the player. In the game's vision, enemies would roam the laboratory. The player would have to gather various items that will help them on their journey to escape the lab. After getting an idea of the game, many key points and features came to my attention, including the player controller, enemy AI, Inventory System, and Crafting System. All those were going to be heavy tasks for this project. After discussing with the other members in the group, we concluded that the hardest feature to develop would be enemy AI since it needed to include multiple behaviors and enemy types, and we all had previous experience programming enemy AI. I took on the task of learning how t...
Read more

CAGD 495 - Stumble Sprint #3

Image
  Starting Sprint #3 for Stumble, there were various things that I wanted to get done; personally, I wanted to implement the core game loop and get started on the arena for the game. During the sprint kickoff, there were various priorities that the designer and producer wanted me to get done at the beginning of the sprint, which were modifying the player controller further and changing some keys; these changes were based on the playtests conducted at the end of the previous sprint. It was mentioned to me that during this sprint, we were going to have an animator & rigger for the team, so I wanted to get animations in the game. So, the first thing I started working on was the priorities and adjusting the player controller. I started working on a delay for the diving mechanic. The biggest problem during the playtest was that players were unable to cancel the dive and dive midair again; if you were quick enough, you would get boosted forward just by tapping space quickly. I adde...
Read more