top of page

Escape / Puzzel game

B-Day 1947

Responsibilities

  • Scripting & Prototyping player features and level interactions in Unreal Engine 5

  • Holding playtest sessions & iterating on puzzle

  • Documentation of metrics and creating a flowchart with gameplay beats

  • Designing mechanics for the player & puzzles

  • Improving pipeline to make the level accessible.

  • Creating music and gathering sound effects

  • Task forces included in:
    - Pipeline
    - Gameplay
    - Features

​

S_skipperLogo.png

Project Breakdown

  • Engine: FriendshipEngine (made by us)

  • 4 weeks halfspeed

  • Editor: Unity  

  • Developer team size: 14

Workflow

Preproduction

I made a quick prototype to visually show what was needed for the game experience. Even if it was very low scope and many features were "fake" it still conveyed the message, this was highly appreciated by our programmers. The next step for me was to plan out the level on Miro. I did this to establish what we needed and to get a sense of how the playthrough could be. This also contributed so that our story taskforce wouldn't become bottlenecked.

image (3).png

Beta

Creating guidelines for us level designers and graphical artists to always be able to work in the same scene. Responsibility over creating an asset gym and reassure that all assets followed the metrics we set up, correct pivots and didn't have any errors in engine.

PROJECT SHOWREEL

Feel free to scroll through the images to view our process and in-game scenes that I have been a part of.

!
Widget Didn’t Load
Check your internet and refresh this page.
If that doesn’t work, contact us.
CreditsSP5.png

Reflections

The core of this assignment was to create a pipeline and improve our workflow. For us level designers we made guidelines within Unity's scenes.  During the beta I proposed duplicating the level for set dressing, ensuring consistency in blockout metrics. We implemented a system using "empties" for set dressing and set dress pushed, enabling simultaneous work without scene checked out issues. Making the level always available for our fellow collegues.

 

To make sure that us designers would all have a sense of ownership, I proposed we all did a solo blockout. After completion, we conducted a walkthrough of each level, allowing everyone to present their ideas and receive feedback. 

bottom of page