Group Projects

Seven game projects developed by me and my talented classmates over the course of two years.

Rat & Slash

About

Rat & Slash is a third-person hack and slash rogue-like where you play a small rat fighting hordes of different enemies while getting upgrades and going through randomly selected levels.

Summary

Project Breakdown

  • Project Number: 7

  • Project Time: 8 Weeks Full-Time

  • Team: 3 Level Designers, 6 Programmers, 5 Game Artists, 2 Procedural Artists

  • Game Engine: RatTrap (custom engine)

  • Platform: PC

  • Download Link

This was the final project I got to work on with my group during my time at The Game Assembly, getting to further develop my collaborative and technical skills as a game developer. We also got to use the most developed version of our game engine to create multiple varied levels in terms of feel and look.

Working on this project let me use all the knowledge and experience I’ve accumulated over my two years at The Game Assembly to create multiple levels that look and feel unique to one another. Getting to use everything I have learned at The Game Assembly, to create levels and moments that utilizes various design techniques which lead to fun and engaging scenarios in unique and memorable settings. The variety in each level also helped with making the game a fun rogue-like, as it meant that each level had its own challenges that needs to be played around in order to win.

For this project I was responsible for four levels, which included theme, layout, set dressing, as well as placement of objectives and boss shrines. I also got the opportunity to help my fellow designers with their levels with both suggestions to the layout and set dressing, while also getting help with my levels from the other designers, artists and tech artists whenever I felt stuck. There was also a considerable amount of collaborating with the programmers on the team, which was a challenging but rewarding experience as the teamwork to get the technical aspects of the game feeling as good as possible and working within our levels gave way to a game that feels awesome to play.

This project was the biggest example of the collaborative aspect of game development being the most important factor to get a successful game project made. There was a palpable feeling of excitement from all disciplines within the team of what we could do, which was reflected in the rapid pace we had when developing the game and the willingness from everyone to give feedback and help to make the best possible version of the game. Both helping others and getting help was an incredibly valuable experience, as everyone’s unique perspective and expertise helped shape a fantastic final game project at The Game Assembly.

Walter Volt

About

Walter Volt is a first person shooter where you play as a disgruntled wizard who sets out on a mission to kill the bigoted mayor of Chrometopia.

Summary

Project Breakdown

  • Project Number: 6

  • Project Time: 15 Weeks Half-time

  • Team: 3 Level Designers, 6 Programmers, 5 Game Artists, 2 Procedural Artists

  • Game Engine: RatTrap (custom engine)

  • Platform: PC

  • Download Link

This project gave us the opportunity to further use and develop the engine we were using for the previous project, which let us further get more comfortable and capable with the engine. We also got to request more advanced features which helped with both the people using the engine and people playing the game. Seeing how the engine was developing and the amount of new features we got to work with was inspiring.

Because this project is first person, we had to take in account how the player sees and moves about in the level, which was a fun opportunity to play around with level design techniques and ideas. We also decided to use a single scene for all levels, which led to us having to focus on optimizing each levels with LOD zones to load and unload objects in the scene. This was the first time we had to utilize LOD zones, as the smaller scale of previous projects did not need optimization in the same way, which led to a unique workflow that was developed for creating and iterating on levels.

I focused mainly on the second level, which is set in a factory the player must navigate through that let me try different ways of breadcrumbing the player throughout the level, by utilizing level design techniques, such as bait and switches, as well as features that was implemented in the engine, such as lighting to guide the player through dark areas. I also acted as the tech designer for this project, which consisted of using the visual scripting system to create scripted events and interactable objects, as well as communicating with the programmers about what we wanted to add to the visual scripting. This experience and side of tech design was super fun, as helping my fellow designers with the technical aspect of their levels and getting to help iterate on specific nodes, which really deepened my passion for the tech design craft.

The main takeaway I have from this project is adapting to the situation and working with what you have and how to circumvent restrictions with creative solutions that add to the experience and performance of the game. LOD zones was the biggest example of this, as it helped immensely with performance for the game while letting us keep the giant scale of the single scene for the game. This part of the project helped me get a better grasp of the technical limitations that might occur and how to work around it effectively to make a smooth experience for players.

Spiteful Hangover

Spiteful Hangover is a top down hack n’ slash dungeon crawler where you play as a viking who has awoken from a drunken slumber and must stop an army of undead and Hel herself.

About

  • Project Number: 5

  • Project Time: 14 Weeks Half-time

  • Team: 3 Level Designers, 6 Programmers, 4 Game Artists, 2 Procedural Artists

  • Game Engine: RatTrap (custom engine)

  • Platform: PC

  • Download Link

Project Breakdown

This project spanned the entirety of the autumn semester, which gave me and the team a lot of time to plan out the game and the different locations, levels, and events. It also gave us a lot of time to fill out each level with set dressing and iterating on the layout, scenarios and encounters of each level. As our reference game was established early in the project, creating the greybox for each level was something that could be started on early, setting the foundation for each level to be worked on for the rest of the project, which helped us when new features that changed how we worked was introduced.

While we worked on this project, our programmers built out a custom engine for us to use during this project and future projects. With the experience of the previous projects, it was great to collaborate with the programmers to add features we wanted to help with our workflow, such as a terrain tool that can be used to shape each individual level’s layout, both horizontally with foliage and objects, as well as vertically with slopes and inclines to make the level layout feel more dynamic and interesting.

Due to unfortunate and unforeseen circumstances and issues that affected the team and the project, the group in its entirety came together to form internal task-forces with the problems we were facing. This let us get fix the various issues efficiently and get the game ready to ship within our set deadline, which otherwise would have made completing the game within the criteria the school had set for us impossible.

The whole project reinforced my belief that communication and flexibility is key to making and shipping a game. This project was the most challenging in terms of sudden problems that was noticed late during development. However, due to the group’s comradery and ability to analyze what needed to be addressed and cut, the game got completed in time, which really showed how incredibly important communication and flexibility is to game development.

Summary

Chef Jeff: Scraps of Hope

Chef Jeff: Scraps of Hope is a top down adventure game where you play as chef who must fight his way through dreams in order to wake up.

About

  • Project Number: 4

  • Project Time: 8 Weeks Half-time

  • Team: 2 Level Designers, 6 Programmers, 4 Game Artists, 2 Procedural Artists

  • Game Engine: The Game Engine (TGA’s in-house engine)

  • Platform: PC

Project Breakdown

This was the second project the team worked on with The Game Engine, which gave us a leg up on workflows and adding features we wanted for the project. Working around the limited camera angles was a fun challenge, similar to Checkmate Go, as many of my original plans for my level had to be reworked on order to accommodate the camera angle and gameplay scenarios. The limitations presented by the camera angle led to some fun and interesting areas and gameplay which challenged me with different techniques and layouts.

Because the game genre was adventure, I wanted to create a feeling of exploring and a sense of what might happen later when seeing something from a distance. An example of this is how I used foreshadowing to show the final arena the player must fight in from the start of the second level, which was my focus for this project. Beside my level and the challenges that presented with it, I also got to give feedback and work on the other designer’s level while he gave feedback and worked on my level, which was an important aspect of fleshing out our levels and improving on issues that both of us might have overlooked.

There were no major hurdles that occurred during the development of the game, either within each disciplines or the group as a whole, which let us create the game without having to change the scope or any specific features of the game. This let each member of the team focus as much as possible on delivering on their tasks and goals, leading to a game that was free on any compromise that had to be made if any issue occurred.

The thing I took from this project is the importance of communication between disciplines in order to fix a workflow that suits the project. This is what the group focused on early in development, which helped us set realistic goals that was achievable for every person in each discipline and which was delivered on by each team member. Whenever something was discovered that could have developed into a major issue later on it was communicated about early to stop it from escalating, which led to the lack of major problems that happened during the project.

Summary

Dejected

Dejected is a 2.5D platformer where you play as two siblings who must navigate and evade mysterious government agents to make their way back home.

About

  • Project Number: 3

  • Project Time: 12 Weeks Half-time

  • Team: 2 Level Designers, 5 Programmers, 3 Game Artists, 3 Procedural Artists

  • Game Engine: The Game Engine (TGA’s in-house engine)

  • Platform: PC

Project Breakdown

This project was the team’s first time working with a custom engine, which came with its own unique and fun challenges. Due to the engine acting as a framework, a lot of communication and was required to add all the features we wanted in order to create the game we had planned, such as 3D collisions and puzzle mechanics. Because we wanted a game that felt like Inside by Playdead, the group wanted a game that felt like it was continuous, which meant both I and the other designer in our group was responsible for one large level each, which led to an interesting challenge of making one level feel varied with different settings, gameplay scenarios and events.

Transitioning my skillset from Unity and Unreal to The Game Engine was a lot smoother than I had initially thought, as many of the features worked similarly to how other engines handle them. With a bit of re-learning shortcuts, key-binds and layout, I could use The Game Engine effectively, which led to quick iterations of my level. Me and my fellow designer also helped each other’s level, which was a refreshing part of the project as we both got to apply our different perspectives to help each other make the other designer’s level more interesting.

As the project went on, the group were behind schedule with the game, which led to us having to shrink the scope we had for the game. While we wanted to have everything we had planned in the beginning for the final release, this smaller scope let us finish the game on time with the circumstances we found ourselves in, which was an important learning moment for me and the team to take with us going forward for other projects.

The most important lesson for me was how communication and scope is very important when working with untested software and workflows, as well as the importance of changing scope when necessary and addressing bottlenecks with taskforces and prioritizing the most crucial issues that appears during development. This project was the most stressful in terms of the amount of issues and features we needed to fix, but getting together to form a plan for getting the project over the finish line was a good experience to learn from.

Summary

Checkmate

Checkmate is a puzzle game inspired by Lara Croft GO where you play as a king chess piece who must navigate through underground ruins and overcome the foes along the way.

About

  • Project Number: 2

  • Project Time: 6 Weeks Half-time

  • Team: 2 Level Designers, 5 Programmers, 3 Game Artists, 2 Procedural Artists

  • Game Engine: Unity

  • Platform: Mobile

Project Breakdown

This was my first time working on a mobile game, which was a rewarding challenge and good learning experience as I had never worked with the constraints of mobile before. I also acted as project coordinator for this project, which let me further develop my skills as a problem solver and team leader. Leading the group and getting the opinion on every team member to come to a conclusion and action that needed to address whatever issue occurred during development was, in my opinion, the most important factor when it came to being a project coordinator.

For the level design aspect of this project, coming up with fun and intuitive puzzles was an incredibly fun process, from using paper prototypes to building all stages in Unity. Due to the many concepts the team came up with I had a lot of puzzles I could set up for each level, which led to a variety of different levels that could be made for a challenging and fun puzzle game.

It was also an interesting challenge to work around the limitations of mobile platforms, as much of the game had to be optimized in order to work on phones and tablets. The unique perspective was also a fun challenge, as verticality, illusions and camera movements in certain levels made for fun and interesting levels to complete.

The biggest takeaway I had after this project was the importance of working around constraints and limitations to make a game better, both technical limitations with hardware that can not utilize certain features that might be taken for granted with PC/console development, and gameplay limitations, such as fixed perspectives and mechanics that are appropriate and fun on a small phone screen.

Summary

Last Unit

Last Unit is an endless runner inspired by Race The Sun where you play as a robot tasked with finding the optimal spit to plant the last living organism on earth.

About

  • Project Number: 1

  • Project Time: 6 Weeks Half-time

  • Team: 3 Level Designers, 6 Programmers, 4 Game Artists, 2 Procedural Artists

  • Game Engine: Unity

  • Platform: PC

Project Breakdown

This was my first project at The Game Assembly, and it gave me a good base insight on how multi-disciplinary communication and workflow works similarly in the industry. For this project I took my idea for a layout to a playable and balanced level by getting feedback from other disciplines in my team and iterating on the layout, placement of items and aesthetic details that helped make the level a fun and challenging ending to the game.

I worked closely with artists to come up with an aesthetic and unique assets for my level. I also worked with programmers and artists to implement special features that only appear in my level, specifically the rolling boulders that can kill the player. This was very rewarding contribution to do and see, as the process of communicating made the process of implementing it easy.

Beside my level design duties, I took on the role as project coordinator for this project, which meant I was responsible for handling communication and helping out with any issues that occurred during development and communicating with our teachers. This responsibility was a fun addition that ensured that everyone got what they needed and felt heard and seen with their issues and ideas.

The most important things I learned from this project is the importance of communication in the team throughout the development of the game. This is the first of many projects that would emphasize how much communication factors into making a successful game, with everything from small things, such as helping others with showing them how certain features work to improve the workflow, to large things, such as meetings with the team to discuss what is needed for each discipline to deliver on their tasks and goals.

Summary