Trailer

Floor Plan Map(2D Top Down Map)

1 Floor Map Iteration

2 Floor Map Iteration

Miro Board

Blueprint Gameplay Mechanics Showcase

Blueprint Implementation in Blockmesh Design
The following section demonstrates how I implemented the core gameplay mechanics in this blockmesh using Blueprints. This showcases how I achieved functionality and how it is presented within the level.

Inventory System

Inventory System Blueprint Functionality:

Players can press Tab to open the inventory system and view all the items they've picked up.

Inventory System Management

Inventory System Blueprint Functionality:
This system allows players to press Tab to open the inventory and view all collected items. Players can only use the correct items in the correct locations, adding logical depth and puzzle-solving elements to gameplay. When hovering the mouse over an item, a tooltip with a description appears, giving players contextual information and enhancing usability. All features are implemented using UE5 Blueprints, with attention to clean logic flow and user-friendly design.

To control item usage logic, I implemented numerous Boolean checks to verify the player's position and ensure items are used only where appropriate.

AI Behavior Tree

AI Zombies:

I created a basic AI system with simple core functionality using UE5 Blueprints. I used the Zombie animations from the Zombie Starter – Mocap Pack. The AI zombie patrols the level automatically and chases the player upon detection. Additionally, I implemented a stealth kill mechanic that allows the player to kill the zombie from behind. Together, these features create a basic zombie enemy that can patrol, detect, chase, and be stealth-killed, all fully built with Blueprints.

CODE DOOR

Code Door Functionality:

I created a code-locked door system entirely using UE5 Blueprints. It includes several core features: players can clear their current input, exit the code door UI by pressing X, and receive immediate visual feedback based on their input. When an incorrect code is entered, the UI flashes red to indicate failure. If the correct code is entered, the UI flashes green, and the door unlocks and opens. I used an array to store the correct password sequence and compared it against player input in real time. The system combines string and array logic, Boolean checks, and timeline animations to handle UI feedback and door behavior.

Art Room Puzzle:

Checker:
The checker function is called each time the correct item is placed on a stand. Its purpose is to check whether all stands have the correct items placed on them.

Puzzle Logic:

Four Box Collisions are used to ensure each stand operates independently. The item display order on each stand is controlled using a percentage-based logic. When the correct item is displayed, the checker function is called; if the item is incorrect, a Boolean is set to false. A Boolean value of true indicates the correct item is placed on the stand.

Art Room Puzzle:

In this puzzle, the player must place two silver swords, one book, and one gun on four separate stands. When all items are placed correctly, a hidden passage opens

Implementation Highlights:

Used four Box Collisions to make each stand detect items independently
Each stand tracks item placement using a percentage-based variable to control correct order
On every item placement, a checker function is called to verify if all four items are correctly placed
When correct, the system triggers an event to open the next path

Look-at Mechanic

A mechanic will force the player to look at a specific item in the scene.

Mechanic Logic:

When the player overlaps the collision box, the Item blueprint will send a message to the Third-Person Character through the Blueprint Interface.
The character is then forced to rotate and face the target Blueprint Item Actor.
Looping the function keeps the player’s view locked onto the item.
A delay is to ensure to create a gap, allowing the player to break free from the forced look-at state after a short period.

Design Rationale:
This feature was created based on feedback from playtesting. During tests, players often missed important notes placed on the ground. The dark lighting in the level, combined with the player's focus on the flashlight beam, made it easy to overlook small environmental clues.
Forcing the player's view toward key items proved to be the most effective solution after multiple iterations of testing.

Map Mechanic

Mechanic Logic:

Red markers on the map UI are bound to specific items in the level via event bindings
When the player picks up the corresponding item, the red marker disappears
For rooms containing multiple items, a checker function is used to ensure that the red marker only disappears once all required items in that room have been collected

Design Rationale:
This mechanic was added based on playtesting feedback. Players often couldn’t tell whether they had missed picking up a key item or simply hadn’t used the correct one. To reduce confusion, this system was developed specifically for that scenario.

Iteration & Wow moment Showcase

Prayer Room Iteration

This change is made to highlight the storytelling aspect of the Dog Tag. The goal is to help players build a connection with the red figure they encountered earlier, so they can better associate the Dog Tag with their teammates' souls.

Office Room Iteration

In the West Office, I noticed during playtests that players often failed to realize they had passed through this area before. So, I redesigned it to leave a stronger impression and make it more memorable for the players.

G virusRoom Iteration

Previously, the G-Virus room felt like just an ordinary room. I enhanced it with more lab-themed visual designs to strengthen its identity as a laboratory.

Freezer Event

After picking up a red key from a corpse, the iconic air raid siren from Silent Hill begins to sound. The player is then teleported into an alternate version of the room, where they encounter "Big Guy". Then the Player teleports to the original space.
Just as the player thinks they’re safe and exits the room, the siren blares again—"Big Guy" bursts through a wall, reappearing for a second surprise encounter.

Trailer

Floor Plan Map(2D Top Down Map)

Miro Board

Blueprint Gameplay Mechanics Showcase

A mechanic will force the player to look at a specific item in the scene.

Mechanic Logic:

When the player overlaps the collision box, the Item blueprint will send a message to the Third-Person Character through the Blueprint Interface.

The character is then forced to rotate and face the target Blueprint Item Actor.

Looping the function keeps the player’s view locked onto the item.

A delay is to ensure to create a gap, allowing the player to break free from the forced look-at state after a short period.

Mechanic Logic:

Red markers on the map UI are bound to specific items in the level via event bindings

When the player picks up the corresponding item, the red marker disappears

For rooms containing multiple items, a checker function is used to ensure that the red marker only disappears once all required items in that room have been collected

Design Rationale:
This mechanic was added based on playtesting feedback. Players often couldn’t tell whether they had missed picking up a key item or simply hadn’t used the correct one. To reduce confusion, this system was developed specifically for that scenario.

Iteration & Wow moment Showcase

WalkThrough

ZHUOYI HUANG Technical LEVEL DESIGNER

Trailer

Floor Plan Map(2D Top Down Map)

Miro Board

​Blueprint Gameplay Mechanics Showcase

A mechanic will force the player to look at a specific item in the scene.

Mechanic Logic:

When the player overlaps the collision box, the Item blueprint will send a message to the Third-Person Character through the Blueprint Interface.

The character is then forced to rotate and face the target Blueprint Item Actor.

Looping the function keeps the player’s view locked onto the item.

A delay is to ensure to create a gap, allowing the player to break free from the forced look-at state after a short period.

Mechanic Logic:

Red markers on the map UI are bound to specific items in the level via event bindings

When the player picks up the corresponding item, the red marker disappears

For rooms containing multiple items, a checker function is used to ensure that the red marker only disappears once all required items in that room have been collected

Design Rationale: This mechanic was added based on playtesting feedback. Players often couldn’t tell whether they had missed picking up a key item or simply hadn’t used the correct one. To reduce confusion, this system was developed specifically for that scenario.

Iteration & Wow moment Showcase

WalkThrough

ZHUOYI HUANG Technical LEVEL DESIGNER

Blueprint Gameplay Mechanics Showcase

Design Rationale:
This mechanic was added based on playtesting feedback. Players often couldn’t tell whether they had missed picking up a key item or simply hadn’t used the correct one. To reduce confusion, this system was developed specifically for that scenario.