NPC patrol and tracking system ：

This was my first time working with an enemy AI system, so I used these two videos to get a basic understanding of how to build one. I then organised my thoughts and, based on my own understanding, built a simple enemy AI system.

Player Pickup System：

Following this tutorial, I learnt how to calculate the detection range and the grab range. I summarised the blueprint approach outlined in the tutorial and adapted it, modifying the trigger key and the distance between the item and the player after grabbing, and successfully implemented the feature independently.

Player nervous bar UI and increase and decrease nervous：

As I had no prior experience with UE5, I wasn’t sure how to create a UI interface in the software. I learnt the process for creating UI interfaces in UE5 by following the first tutorial. Based on my understanding of the game, I created a simple health bar UI.

Through the second tutorial, I gained an understanding of the concepts behind health gain and health loss blueprints. Based on my summary and reflection on the tutorial, I felt that the approach to health loss blueprints was overly complex, so I independently developed a simpler health loss blueprint.

After I finished the blueprint, two issues arose: 1. The health-restoring blueprint did not work on NPCs. 2. I had set the health to decrease by 10 each time, but in the game it dropped straight to 0. I discussed these issues with Ross and we resolved them.

Checkout and Door-Opening System：

Through this tutorial, I learnt the approach to creating door-opening animations. Following the tutorial’s guidance and adjusting the values, I completed the animation for opening and closing the door.

I built a separate checkout (item quantity detection) blueprint from scratch, and I connected these two separate systems according to my own approach to form a fully integrated, interconnected system.

Character Dialogue System：

I came across many different types of dialogue tutorials, studied them, summarised their blueprint approaches, and identified their core commonalities. I extracted the blueprint approaches I needed from the tutorials and combined them with my own ideas to complete the dialogue system.

After completing the Blueprint, I changed the dialogue text. However, when the game ran, the dialogue text hadn’t been updated and remained the original version. I asked Ross, and he told me that I should click on the object that triggers the dialogue and change the text in that object’s details panel, rather than changing it in the Blueprint variables.

Shopping Car System：

This tutorial gave me an idea: the concept behind this feature is that objects can only be pushed or pulled along the ground and cannot be picked up. So I realised that I already had a blueprint for picking up objects; I simply needed to lock the Z-axis to ensure that objects could only be pushed or pulled and not picked up. I added a check to the pick-up blueprint so that the Z-axis is locked whenever a shopping trolley is detected.

Shopping List System：

From this tutorial, I learnt how to convert a PNG image into a texture, and I learnt how to add animations when creating UI elements.

Mini Game System：

If the mini-game requires players to progress through levels, I need to ensure that the game can save their progress, which involves quite complex operations.

However, I’ve found a jigsaw puzzle mini-game created using user controls; when the game is triggered, it simply opens and closes the canvas panel, so there’s no need to save player data.

The issue I’m facing is that when the mini-game is triggered, the player’s movement and camera view are locked, but even after the mini-game ends, the player is still unable to move.

I consulted Ross and resolved the issue. The problem was that the player became locked in place once the mini-game was triggered, but my Blueprint required the player to be locked in place again before they could be interacted with it was impossible to trigger the mini-game twice. So I moved the action to unlock the player to just before the Blueprint that closes the mini-game. The Blueprint now works by first unlocking the player once the mini-game is complete, and then closing the mini-game.

NPC Dialogue System：

The system works fine, but UE5 throws an error when the game is closed. After consulting Ross, I found out that the error is caused by the player overlapping with the collision volume too many times; although the dialogue has been removed, the command to remove it is still being triggered. Ross therefore advised me to add a condition in the Blueprint to prevent it from being triggered multiple times.

NPC Animation：

This is a tutorial on creating a 2D platformer using UE5; this section focuses on creating 2D character animations. I have used the approach mentioned in the video to assemble the animation frame by frame.

As I am using the default character model in UE5, I cannot simply delete the static mesh, nor can I directly apply the animation to the default static mesh. So, I added a PaperFlipBook component; both components appear simultaneously, but the default static mesh is hidden. Although both components exist, the player can only see the 2D character.

Cut Scene system:

This video primarily demonstrates how to play a video in full-screen mode in UE5. I have independently developed the Blueprint logic for the entire cutscene. My approach is to play this video before the player transitions to the next level, and once the video has finished, the player moves on to the next scene. As the video is placed within a User Control, after creating the video as per the tutorial, I added a Blueprint to create a Widget and add it to the viewport before the level transition Blueprint.

Although the Blueprint is running, the video is displayed as a static image in the viewport and cannot be played. I discussed this issue with Ross, who explained that as the video is 5 seconds long, the delay added in the Blueprint must be longer than or equal to the video’s duration; otherwise, the widget will be displayed in the viewport for too short a time, and the video will not play.

I encountered an issue with cutscenes during the build process; specifically, the videos went missing after the build was successful. After doing some research, I discovered that whilst the folder containing my cutscene videos was named ‘cutscene’, the folder for storing videos in UE5 is named ‘Movies’, and the videos could not be included in the build. I therefore renamed the folder and updated the video paths.