Alice Through the Fey Realm
Dive into the mesmerizing world of "Alice Through the Fey Realm," an isometric narrative adventure that casts you as Alice on an unforgettable quest. Trapped in this mystical realm, your mission is clear: find your way home. Explore this new world, complete missions and talk to various fantastical individuals along the way. Will you unravel the secrets of the Fey Realm and guide Alice back to reality, or will the enchanting mysteries of this magical world forever alter her destiny?
In this student project I took over the role of design lead, taking responsibility of a variety of things such as documentation, group management, stakeholder communication and more. I also took over the design and implementation of the 3Cs and the game’s audio.
~ 20 Devs
32 Weeks
Narrative Adventure
Unreal Engine 5
PC (Steam)
University Project
Design Lead
As design lead, I had the responsibility of managing a team of around 8 game designers. I prepared documentation pipelines, communicated with stakeholders and other disciplines, checked in on progress and adjusted priorities.
System Design
Besides my work as design lead, I also took on smaller system design and implementation related tasks across the course of the projectm such as the design and implementation of the 3Cs or utilities in the custom dialogue and mission plugin from our programming team.
Audio
Making use of various available asset packs and some newly created assets, I designed and implemented all of the audio in this project. By making use of UE5 Meta Sounds, I was able to create a rich and enthralling soundscape.
Lead Responsibilities
This project gave me the chance to take up a role I have never taken up before. As design lead I had a wide variety of responsibilities:
Communication: I acted as the first point of contact between the development teams different disciplines. This required me to stay up to date with the progress of the design team and stay in close contact with the other discipline leads, so that I would always have a clear overview of the current state of things. Together with our producer, us discipline leads would also attend lead meetings with the teaching team, who acted as our projects stakeholders, and prepare and present regular update presentations to them.
Planning & Decision Making: As design lead I was also directly involved in the planning processes of the project. Together with the rest of the lead team, I would fill the project backlog and set sprint goals based around our projects priorities and available manpower and skills, making sure that stakeholder feedback and notes from build reviews and sprint retrospectives would always be taken into account. Sometimes, interests from the different disciplines would clash, and hard decisions had to be made around things such as scope.
Priorities & Pipelines: I was also more directly involved in the day to day workings of the design team. As priorities shifted across the duration of the project, I made sure that the focus of each developer was on the right tasks, assigning specific tasks to specific people if necessary. I also made sure to intervene more directly if I saw the need for it, by, for example, providing the team with a documentation pipeline in order to streamline the development process.
Here you can see one of the examples of the above mentioned pipelines. The image below is part of what I provided the narrative design team with, as they did not have a documentation pipeline for mission design yet. I provided them with a simple template of a mission graph with specific symbols and colours for things such as dialogue and mission objective updates. From that point onwards the narrative designers created mission breakdowns for each designed mission, as can be seen by the mission graph example. This significantly improved the speed and efficiency at which mission were able to be designed and implemented, and improved the communication within the narrative design team.
