Pumpkin Plot Plunder

---

Overview

Pumpkin Plot Plunder was conceived during a skills challenge as part of my coursework. We was tasked with creating a game within 8-weeks and was given the theme of Autumn Harvest. Our team chose to make a chaotic management game were players are tasked with ensuring their growing pumpkins are watered and harvested in time before they turn evil. Although we initially considered a Roguelike approach, time constraints led us to focus on refining the core mechanics of pumpkin management and harvesting.

The project ended up winning the overall prize for the skills challenge

Demo

Lessons Learnt

• Scope Management: In hindsight, we should have further reduced the scope of the project to prioritize refining the core gameplay mechanics. By focusing on fewer features, we could have spent more time ensuring that each feature felt polished and engaging
• Feedback and Immersion: We realized the importance of having visual and audio effects/cues to enhance player feedback and immersion. For instance, implementing visual cues for pumpkin attacks would have made the gameplay more clear and fair for players
• Early Playtesting: We recognized the value of involving playtesters earlier in development. Their feedback could have helped identify potential issues and opportunities for improvement, resulting in a better game by the end of the project
• Designer-Friendly Systems: One of the key takeaways was learning how to create systems and actors that are easy for designers to interface with, while requiring minimal support. This skill not only improves collaboration within the team but also streamlines the development process, leading to more efficient iteration and refinement of features/mechanics

What I Did

• Setup hub github repo with required GitIgnore so we could all contribute to the project. (Git used as its free and quick to setup)
• Created pumpkins with state system
• Created multiple interfaces for Damage, Interaction, Watering and Using (Activating)
• Created multiple blueprint callable functions that could be used by designers to play sound or create UI
• Created basic UI to walk to the player (Ran out of time to polish this better as the pumpkin walk speed changed last minute)
• Mentored other members on the team how to use Git and some parts of Unreal Engine such as blueprints

Code:

The code for this project can be found on my Github

Close

Toyboxtitans

---

Overview

Toybox Titans is a 3 vs 1 multiplayer game set in a kids' bedroom. The objective is to destroy the defending toy in their crafted arena. After learning about the project from peers at CG Spectrum, I joined the team to contribute to creating a vertical slice. Over four months, myself and 20 other team members dedicated our efforts to designing, creating, and testing the game. Although there isn't footage from playtests available, the demo video provides a glimpse of some of the features I worked on and implemented.

Demo

Lessons Learnt

• Adoption of Industry Standard Tools: One of the key takeaways from the project was learning how to use the industry-standard tool Perforce for version control. This experience provided valuable insights into collaborative development workflows and improved project organization and management
• Multiplayer Gameplay Implementation: I learned to implement gameplay features with multiplayer considerations, ensuring smooth functionality for all players. For instance, when implementing projectile mechanics, I used techniques like lerping to maintain smooth visuals across multiplayer sessions. This experience emphasized the importance of designing features that work seamlessly in multiplayer environments
• Utilization of Unreal's Gameplay Ability System: A significant learning experience from the project was understanding Unreal Engine's Gameplay Ability System. This provided a robust framework for implementing player abilities and managing gameplay mechanics, enhancing the game's depth and complexity
• Reflection on Ranged Implementation: In hindsight, I identified opportunities for improvement in the ranged implementation. Splitting the ranged abilities into separate ability classes for each fire mode would have enhanced maintainability and organization, addressing issues of complexity and facilitating easier updates and adjustments

What I Did

• Setup Perforce within Azure cloud for the whole team
• Created combat mechanics using GAS (Melee
• Ranged and Throwables)
• Implemented designer changable UI that hooked into Game logic e.g changing icon when ability is inactive
• Created shaders to see some characters through the wall
• Created shader for invisible wall that would only display when the player is close to the wall
• Created camera modifiers to change camera behavour based on designer requested
• Created simple blueprintable interface for the ability system that our designers could use to minimise there needed knowledge of the gameplay ability system
• Worked closely with design to create configurable systems and gameplay elements that could fix player requirements
• Created a series of tutorial videos to document how to modify values and what those values do

Code:

Code snippets are available on request

Close

Tower Defense

---

Overview

After discussing my desire to create a game in Unreal Engine, my mentor suggested building upon the base Unreal Strategy game provided by Epic. Luckily, my mentor had upgraded the strategy game to work with Unreal Engine 5, making this project my first experience with the latest Unreal version. I established several goals for the project, including updating wave behavior, modifying the functionality of the arrow turret, and implementing a third-person mode within the game.

Demo

Lessons Learnt

• Integration of Blueprints with C++: Through the tower defense game project, I gained a deeper understanding of the various methods by which Blueprints can interact with C++ code. This experience allowed me to leverage the strengths of both scripting and programming languages to create more robust and flexible game systems
• Character Switching and Control Scheme Implementation: A significant learning experience from the project was implementing character switching mechanics and associated control schemes. This involved understanding the various methods of possessing minions within Unreal Engine and implementing a seamless return to the original minion when necessary
• Reflections on Input System Rework: Reflecting on the project, I identified opportunities for improvement in the input system. Given additional time, I would prioritize reworking the input system to utilize enhanced input, which is the current standard. The custom input implementation inherited from the base Epic game introduced avoidable bugs and limitations, underscoring the significance of adopting standard input solutions for smoother and more reliable gameplay experiences

What I Did

• Added new wave start called buying where players will be able to buy towers without the threat of an on going wave
• Created ready up mechanic to allow the player to build towers before the start of the first wave
• Programmed simple UI to inform the player that they needed to ready up
• Changed how the arrow turret worked by making it only fire in bursts when an enemy enters it's attack range
• Spawned a minion for the player to play as while a wave is on going

Code:

Code can be found on my Github

Close

The Cube

---

Overview

The Cube was a team project challenge set by CG Spectrum. Teamed up with a game designer, we set out designing and creating a game that would push the boundaries on what we already knew. This was my first game project in Unreal Engine and thus was also my 1st attempt at implementing an algorithm to dynamically spawn actors within the engine. This experience presented both challenges and opportunities for growth as I navigated the intricacies of Unreal Engine and honed my skills in algorithmic implementation.

Demo

Lessons Learnt

• Dynamically spawning Actors: One of the key technical challenges I tackled during the project was learning how to spawn in actors dynamically. This required me to take a step into the dark and learn how different parts of the engine worked that I hadnt seen before. I managed to successfully implemented this which is one of the key highlights of the project
• Maze Generation with Loop Erased Walk Alorithm: Reflecting on the project, I gained valuable experience in maze generation techniques, mainly through my implementation of the loop erased walk algorithm. Learning this has expanded my understanding of procedural content generation and its applications in game development
• Importance of Bettter Control Design: In hindsight, we should have spent more time refining the controls and the feel of moving the maze around, as the final game had lackluster and frustrating controls. This led to the game not being as enjoyable as it could have been. Although the game is technically sound, the controls were a significant drawback. If given the opportunity to redo the project, I would allocate more time to ensure that the controls are satisfying and contribute positively to the overall gameplay experience

What I Did

• Created a structure spawner to be used with a maze generation algorithm
• Programmed a maze generation algorithm using loop erased walk (wilsons algorithm)
• Configured a ball object to be able to move through the maze based on rotation
• Created player controls to move the ball by tilting the maze
• Created end portal which when activated changed the level to the end game screen
• Taught designer parts of the unreal engine and gave simple tasks to showcase learning opportunities

Code:

The code for this project can be found on my Github

Close

Console Fps

---

Overview

The Console FPS project was created during my Introduction to Programming course at CG Spectrum. Inspired by classic Wolfenstein games, which shared similarities with the course project (albeit rendered top-down), I sought to enhance the course material by transitioning it into a first-person perspective. This initiative led me to explore and implement a ray casting game renderer within the constraints of the course project, resulting in a significantly improved final game.

Demo

Lessons Learnt

• Application of C++ in Game Development: Through the Console FPS project, I gained valuable experience in applying my knowledge of C++ to game development. This involved understanding core programming concepts and implementing them within the context of game design, further solidifying my proficiency in the language
• Creation of a Ray Casting Renderer: One of the major learning experiences from the project was the development of a ray casting renderer. This involved researching how ray casting renderers work and implementing them to create a functional game renderer. This hands-on experience not only expanded my technical skills but also deepened my understanding of game engine architecture
• Utilization of Maths in Game Development: Another significant takeaway from the project was the application of mathematics in game development. It served as an excellent opportunity to refresh my mathematical knowledge and explore its practical use in game development contexts. Through tasks like implementing collision detection, rendering, and player movement, I gained a deeper appreciation for the foundational role of mathematics in game development. This experience not only reinforced the importance of mathematical principles but also strengthened my ability to address complex game mechanics effectively

What I Did

• Created level editor to allow users to create their own ingame levels
• Saved levels into a file
• Allowed users to select a level file to play
• Created a ray cast renderer
• Implemented colour into the renderer
• Implemented basic sound through the beep function

Code:

Code snippets are available on request. I am also happy to provide the whole project

Close