CAGD 470 - LockedIn Sprint #6

 During the sprint kickoff, the main objective was to polish enemies further and start making them work with the other features implemented in the game. So, a couple of points were the jumpscare, a watcher vision fix because it had some inconsistencies with the player looking at it, and finally, adding an enemy item drop when killed.


I started by tackling what I considered one of the most challenging features to fix. I started by identifying the problem. At first, I thought it would be a problem with the vision detection; however, the problem was in the state machine, and there was an error in the prioritization of each state. After tweaking the code, I realized that the problem was more in-depth in Rage mode, which was taking priority over all roles even when it lost the player in sight. With this taken into account, I could fix the issue, and it was now working as intended.



After working with the watcher, it was time to address another missing feature: nothing was dropped when the player killed an enemy. This feature needed to be implemented to allow the crafting in the game to work. So, I started by developing the death drop feature. I needed to know precisely what the designer wanted in this feature. After a short meeting, I had all the information I needed to develop the feature. The designer needed a random generator between two variables and also to choose between a list of possible material prefabs. So, with that In mind and having the modular death previously implemented, it was easy to hook onto any enemy.



With this feature done, I started looking at something essential that was missing from our game, which was the main menu. After talking to the producer, we realized that we didn’t have cards for this, so I made it an essential part of our sprint. So, I started developing it; there was a wireframe in the GDD that I could take advantage of; however, after talking to the designer, we modified it and adjusted it to fit the game feel. I also took the chance to add it to the settings menu. So, with all that discussed, I started developing it and incorporating new sprites into the game and a new Logo.  This was the menu for Locked In:



I wanted to add some additions I’d never done before, such as resolution configuration, which meant doing full screen, windowed, and borderless, as well as changing the resolution to the user’s liking.


With that in place, I started working on one of the final feature implementations of the game, which was jumpscares. The game needed a way to scare the user, and out of all the enemies, I chose the watcher since it's an enemy that attacks the player from the back, giving the watcher more freedom to do a jump scare. I decided to make the Jumpscare in the UI, and after spending some time rendering the watcher and editing the graphics in Photoshop, I got two pieces and animated them in the game engine for a quick jump scare.



Overall, this sprint went fantastic; some unseen hurdles, like the main menu, needed to be implemented during this sprint. So I spent some unseen time there. However, it was necessary, and I added the resolution and window selection, which I’ve never previously implemented. My performance on this sprint could have been better, but it turned out remarkably well out of everything I had developed. With this sprint done, we have a clear view of the finish line, and we are ready to start the final sprint for Locked In.

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