Genre - 3D Platformer
Engine - Unity / C#
Team Size - Solo
Development Time - 12 Weeks
Progress - Continued
Design Documentation
Out of Water is a 3D platformer developed as part of a three-month university project aimed at exploring How Locomotion is Handled Under and Above Water. Inspired by genre-defining classics like Spyro the Dragon, Crash Bandicoot, and Banjo-Kazooie, the project was set to blend the best elements from these titles into a fully playable demo. The game presents players with two distinct movement systems: the fluidity of underwater exploration and the precision of traditional platforming on land.
Project Goals
Overview
For this project, I aimed to establish a foundational base that I could expand into a more comprehensive showcase of my skills in game-play, level, UX, and UI design.
I used asset packs from around the web to complement my skills, allowing me to concentrate on my strengths without getting bogged down by aesthetics. Everything you see—programming and design—is my own work, while visual assets like the main character and icons were outsourced.
Throughout this project, I completed four distinct sets of assignments, each accessible via the links below.
Goals
Design and implement a fluid player movement system compatible with both controllers and mouse/keyboard.
Develop a seamless camera system that complements player movement.
Create a basic, yet stylish user interface suitable for a 3D Platformer.
Design a basic grey box level that showcases the movement of the main character
Complete a prototype playable demo of “Out Of Water”
Stretch Goals
Apply a simple art pass to the level, providing a vertical slice of the world’s aesthetics.
Implement AI enemies and obstacles for players to avoid.
Add NPCs that players can interact with throughout the level.
Add NPCs the ability to give quests to the player
Integrate audio/visual feedback, including sound effects, music, and VFX.
Ensure the prototype is fully playable and performant on the Steam Deck.
All project goals and stretch goals were completed, except for adding quest functionality. I believe this was due to time constraints and over scope of the project - alongside having the opportunity to showcase my project at ExpoTees and the required work that this entailed.
Reflecting on the outcomes of this project in relation to the initial goals I set, I believe it has been a success.
The primary objective was to establish a solid foundation for further development, and I feel that I have achieved that. This small vertical slice serves as a strong demonstration of my ability to conceptualize and create within a limited time-frame. I am proud of the enjoyable experience I’ve crafted, and I am confident that it has the potential to evolve into something much larger and more impactful.
However, I believe that it could have benefited from a little more concentration in different areas :
More Fleshed Out Narrative
A compelling story with strong individualistic characters provides players with a clear motivation to collect items and complete challenges. When players understand the stakes or the journey behind their actions, it makes collecting items feel meaningful rather than repetitive - this is something that I believe that this vertical slice misses.
More Refined Level Design
More time spent on refining the level design in a block-out phase would have allowed further time for play-testing and feedback which would have lead to a better paced level.
These both are aspects I know I can rectify, and will do so in the short future.
ExpoTees
I chose the Agile development sprint framework to ensure I could manage the project effectively within a flexible, structured workflow. By breaking the project into focused, iterative sprints, I could prioritize regular check-ins on my progress and incorporate improvements efficiently. This approach allowed me to refine key elements like gameplay mechanics and visuals in manageable phases, adapting quickly to any new insights or challenges without compromising the project’s timeline or quality.
The sprint structure also helped me stay organized and motivated, with each sprint marking a milestone for specific features or tasks. By setting clear, achievable goals for each sprint, I maintained a steady pace and had a clear roadmap for balancing different aspects of the game. Working alone, the Agile framework provided a disciplined yet flexible structure that kept the project cohesive and aligned with my vision for the final experience.
I had the opportunity to present my project at ExpoTees 2024, Teesside University’s annual showcase event that brings together students and industry professionals. This event allowed me to display my work to over 100 companies from across the UK, offering a platform for recruitment and networking. Presenting my game at this prestigious event was a valuable experience, giving me direct feedback from industry experts and the chance to demonstrate my design and development skills in a professional setting.
It was during ExpoTees that I realized Out of Water was more than just a university project. Seeing players interact with the game, smiling, and genuinely enjoying the experience was a turning point. Their positive reactions inspired me to take the project further and explore its full potential beyond the classroom.
Research / Testing
To explore the intricacies of underwater movement, I dove into existing games to better understand why underwater levels tend to be unpopular. Two key reasons emerged:
Resource Management: Many games limit the time a player can spend underwater through a constantly draining oxygen meter. While this creates tension, too much of it can overwhelm players, turning the experience into a source of stress.
Imprecise Controls: Games like Mario showcase tight, responsive movement on land, but once underwater, the controls often become awkward. That classic "button mash" to swim upward and the slower, floaty turning mechanics can make underwater navigation feel clunky and frustrating.
By learning from these tests, I aimed to craft a more enjoyable underwater experience.
After playing through an extensive list of 3D platformers, I compiled a detailed list of key aspects that could inspire my own work. Each game offered unique insights, helping shape the direction of my design.For more insights into my discoveries, check out my weekly development blog through the link below!
In the project's early phases, I adopted a Scrum Agile framework, incorporating short development sprints followed by feedback sessions. This approach enabled rapid iteration, allowing me to gather insights from peers after each sprint and ensuring the project stayed aligned with its vision. Creating an engaging character controller was a highly iterative process, tested consistently through weekly lab sessions with peers, lecturers, and supervisors, as well as feedback from random users on Itch.io. Their insights helped refine the turtle's handling, ultimately leading to an intuitive character that is easy to pick up and play.
