Game Development Task 3
22/4/2025-31/7/2025 Week 1-Week 14
Jie Xuan/ 0356515
Game Development/ Bachelor of Creative Media/Taylor's University
Game Development Task 3
TABLE OF CONTENTS
1. Instructions
INSTRUCTIONS
GAME DEVELOPMENT
TIME FRAME: WEEK 08 - WEEK 10
Task 3: Game Prototype
Description:
Students given the task to create the prototype of their game.
The prototype doesn’t need to have the final art asset, and theuse of grey boxing is allowed. The focus here is to quickly test out the game mechanics and to troubleshoot any technical difficulties discovered during the development. The focus should be the MVP of your game.
This includes:
Coding movements and actions
Coding obstacles and enemies’ interactions
Coding game levels (Logic of the game)
Submission:
Video walkthrough and presentation of the game
Online posts in your E-portfolio as your reflective studies
Task 3: Game Prototype
A. UI Map Input Progress
Here are some tutorials that help me:
I insert the map first and than I sort the layer and rename the layer.
B. Character Input Progress
After inserting the map I do the character animation, which included creating the Swim animation, Hurt animations and when win status will have Change animation for the Main Character. These animations were imported into Unity, and I created an Animator Controller for the Main Character.
In Level 1, the character appears as a normal swim suit, but as she progresses to Level 2, she transforms into a diver suit. Therefore, in Level 1 I created Animator Controllers for the main character to change the animation base on the trigger I set.
Since Task 3 focuses on the Level 1 prototype, I have showcased only the Level 1 version of the character and its animations. I set up transitions between the animations in the Animator, allowing the character to move left, right, up and down using the arrow keys.
Save character animation:
Animator:
Add parameters.
Add conditions on transitions.
Adjust the transitions in animator
Script Writing:
Player script
C. UI Button Input Progress
Right click Canvas and click on UI and insert image for UI button.
Script Writing:
Health Less when get hurt script
For Level 1 got one bug is when the player get Hit the heart will not get less will fix it on Final Task.
D. BGM Sound Effect Music Source Input
Add on music source for BGM and collect points sound when collect fish.
Add BGM music for game
Collect Point sound effect appear not correct time will debug it on Final Task.
CONTRIBUTION
Jie Xuan:
Level 1 UI Map Input, Character animation progress, UI Button Input, Music source Input, All the script writing.
Final Submission:
Task 3 Outcome
FEEDBACKS
Week 8
Level 1 seems a bit to less item need to add some.
Week 9
-
Week 10
-
Week 11
Task 3 Submission.
REFLECTION
Experience
This task gave me hands-on experience in building a functional game prototype from the ground up. I started by importing the UI map, organizing layers, and preparing the character animation sequences—including swim, hurt, and win states. Using Unity’s Animator Controller, I created animation transitions triggered by key inputs and progression logic. A key challenge was ensuring the character’s transformation from a regular swimsuit to a diver suit was reflected correctly through conditional triggers. I also designed and implemented UI buttons using Unity’s canvas system and wrote scripts for character movement, item collection, and health reduction. Lastly, I added background music and point-collection sound effects, although I encountered bugs with timing that I plan to fix in the final task.
Finding
Through this task, I learned that game development requires both creative and technical precision. Animation transitions must be smooth and responsive, and scripting logic must align with the intended gameplay mechanics. I also discovered that bugs are a natural part of the development process and debugging is just as important as designing. Additionally, I found that planning character states and transitions early helps avoid confusion during implementation. This task deepened my understanding of Unity’s Animator, scripting in C#, and audio management, all of which are critical for delivering a smooth and engaging player experience.
Observation
During the development of the Level 1 prototype, I observed how crucial it is to have a well-structured workflow especially when working with multiple elements such as UI layers, character animations, scripts, and sound effects. Proper naming and organization of layers in Unity made it easier to manage the game structure. I also noticed that even minor bugs, such as the health bar not updating or sound effects not triggering correctly, can significantly affect the player experience and require immediate attention during testing.
Comments
Post a Comment