top of page

Game Download

Crusade

The project, titled Crusade, was developed as a solo endeavour where I took on the role of lead developer. The tools that I utilizing are Unity and Photoshop, my primary goal was to create an engaging Action Role-Playing experience that emphasized key objectives, including multiplayer interaction and a seamless combat system. Throughout the project, I focused on overcoming challenges related to multiplayer implementation, ensuring smooth player interactions and consistent synchronization between the client and server to deliver a cohesive and immersive experience.

Role

Lead Developer

team size 

1 person

development time

6 months

Game Engine

Unity

Genre

Action Role-Play (Souls Like)

Technologies used

image.png

Unity

image.png

C#

image.png

GIT

image.png

Photoshop

image.png

Audacity

image.png

Trello

Theme/Story 

The player awakens in the depths of a ruined dungeon, disoriented and alone. As one of the last survivors of an ancient crusade, they have no memory of the events that led to the dungeon’s destruction. With their comrades likely fallen and the fate of the crusade uncertain, the player must navigate the treacherous ruins, uncovering forgotten secrets and evading mysterious dangers. Along the way, they will discover ancient artifacts—relics of a lost civilization—that hold untold power. Driven by duty, the player must escape the dungeon, recover these relics, and determine if their crusade is truly lost.

Role and Responsibilities

As the lead developer for the project, I spearheaded the design and implementation of essential gameplay systems using C#. My responsibilities encompassed a wide range of key features that contributed to the overall player experience, including crafting intricate player movement mechanics, developing advanced AI behaviors, and overseeing network synchronization to ensure a seamless multiplayer experience.

To achieve this, I implemented a robust poise system that prevents players from being stun-locked during combat, enhancing overall gameplay fluidity. I also designed a two-handed weapon system that allows players to equip different weapons strategically, further enriching combat dynamics. Additionally, I developed an armor system alongside a model-based equipment system, utilizing scriptable objects to manage player gear efficiently and enhance the game’s depth.
In terms of player interaction, I created an item-based pickup system and a fully functional player inventory system, complete with an intuitive user interface. These systems encouraged exploration and engagement with the game world. Furthermore, I introduced a stance system and a stance-breaking mechanic, which added layers of strategy to combat encounters by allowing players to exploit their opponents’ vulnerabilities.

I also implemented a riposte system that integrates critical hit and backstab mechanics, which enhances tactical combat options and rewards skilled players. Throughout the development process, I rigorously tested and optimized each system to ensure not only functionality but also a smooth and engaging gameplay experience for players.

By balancing these various elements, I aimed to create an immersive and challenging environment that keeps players invested in their journey through the game. Ultimately, my goal was to deliver a polished and dynamic gaming experience that meets the high standards of today’s action role-playing games.

Design Process

In developing The Crusade, I followed a five-step design process, which I will elaborate on throughout this portfolio piece. Each phase was crucial in shaping the game's mechanics, systems, and overall player experience.

1

DESGIN DOCUMENT

prototyping

rought blockout/coding

2

3

refinement of code and level design 

4

passover and feedback

5

Design Document

The first step in my design process was creating the Game Design Document (GDD), where I organized all the initial ideas for The Crusade and planned out the key features to be included. In this document, I outlined the core gameplay mechanics, establishing a clear vision for how the game would function and what players could expect in terms of experience and interaction. This foundational step helped guide the subsequent phases of development. 

link to game design doc : https://docs.google.com/document/d/1ndrFRtmu_ZA3SjvNHt5fQmK8QdQM9eJQ1tZDJ3C329k/edit?tab=t.0

Core Game Pillars

  • A customisable player  character

  • Responsive AI

  • ​ruined world environment 

  • exploration 

Gameplay Breakdown

The core gameplay loop involves the player exploring vast environments to discover ancient ruins. Once inside, they navigate labyrinthine layouts, searching for hidden items and battling enemies to grow stronger. As they progress and gain enough power, they take on challenging boss fights. After defeating the boss, the player returns to exploration, continuing the cycle of discovery, combat, and progression. This loop keeps the player engaged through a balance of exploration, combat, and strategic growth.

Explore Ruins

Find ancient artifacts

Fight enemy's

find loot

Second-to-Second gameplay :The player will explore both an expansive open world and the depths of ancient ruins. In the open world, they will search for new areas and hidden secrets, while in the ruins, they will navigate intricate, maze-like environments

Minute-to-Minute gameplay : The player will uncover hidden items and defeat enemies to grow in power, gradually enhancing their abilities and equipment. These elements of exploration and combat are key to the player's progression, allowing them to face increasingly difficult challenges as they advance through the game.

Hour-to-Hour gameplay : The player will face challenging bosses in order to unlock new zones and acquire ancient artifacts. Each boss fight serves as a major milestone, testing the player's skill and progression while rewarding them with access to new areas and powerful artifacts that enhance their abilities and deepen the game's lore.

Level Breakdown

The player begins in a small, confined room that leads into a narrow corridor. Along the way, they encounter three dead bodies, subtly hinting at an unknown threat lurking just out of sight. This design choice creates a sense of tension and unease, drawing players deeper into the environment as they anticipate the dangers that lie ahead.

1

image.png

2

At the end of the corridor, the player discovers a glowing object, which, when picked up, provides them with a sword to aid in their survival. This weapon becomes a critical tool for the player moving forward. As they proceed, they spot another corridor ahead, where two undead enemies are revealed. The player now faces a choice: either engage the enemies in combat or try to evade them and continue exploring, adding an element of strategy and tension to the gameplay.

image.png

3

At the end of the corridor, the player enters a small room with a single enemy, prompting a decision to either fight or flee. After clearing the room, the player ascends a staircase that opens into a courtyard. In the center of the courtyard, there is a small fire pit, which acts as a save point, restoring the player's health upon interaction. From here, the player is presented with three distinct paths. One leads to valuable armor, another to a challenging boss fight, and the third reveals a hidden corridor for further exploration. These options provide both strategic and immersive depth, giving the player control over how they advance through the game.

image.png
image.png

4

In this breakdown, after acquiring the armor, the player chooses to explore the hidden path. As they proceed, they soon realize that the hidden path opens up, revealing even more to discover. This new area presents three additional paths. One leads up a set of stairs, another takes the player toward an enemy, and the last is a small room with a corridor leading further into the unknown. These branching paths expand the player's sense of exploration, creating intrigue and encouraging further discovery as they decide which direction to take next.

image.png

5

In this breakdown, the player weighs their options, picks up another item, and heads up the stairs. Moving through a corridor, they eventually uncover one of the possible ways to end the level: a shining portal at the top of a mountain. As the player walks along a narrow pathway, they spot an opening that reveals a wind to the boss room. From there, they proceed into another corridor, building anticipation as they inch closer to the level's final challenge. This sequence offers a sense of discovery and choice, while also guiding the player toward critical encounters and the level's conclusion.

image.png
image.png

6

The player follows the corridor around, discovering another item and encountering an enemy along the way. After dealing with this, they peer down the final corridor, which leads into even more winding passageways. However, deciding not to continue exploring, the player turns back and retraces their steps to the courtyard, ready to face the boss and take on the challenge that awaits. This decision to return to the central area builds tension, as the player prepares for the pivotal encounter in the game. 

image.png

7

Once the player faces the boss, this is where the tutorial concludes, as the boss ultimately defeats the player. However, if the player had managed to win the battle, they would have been able to proceed to the portal, which would have revealed more of the world, marking the end of the tutorial and the beginning of the larger adventure. This outcome teases the vastness of the game’s universe, setting up the narrative and gameplay to come while also reinforcing the difficulty and challenge the player will face throughout the game.

image.png

Code Example

PlayerNetworkManager Script Overview

This script is a key component of a multiplayer game developed in Unity, responsible for synchronizing player-related data across the network. It leverages the Unity Netcode for GameObjects framework to manage player states, inventory, equipment, combat interactions, and more in a distributed multiplayer environment.

Key Features

  1. Networked Player States

  2. Real-Time Equipment and Combat Management

  3. ​Player Stats Management

  4. Multiplayer Interaction Handling​

1. Networked Player States

  • Utilizes NetworkVariable to track and synchronize important player attributes such as:

    • characterName: The name of the player's character.

    • currentWeaponBeingUsed: Tracks the currently equipped weapon.

    • isTwoHandingWeapon: Indicates whether the player is using a weapon two-handed.

2. Real-Time Equipment and Combat Management

  • Dynamically updates player equipment and weaponry across the network, ensuring consistency in all connected clients.

  • Includes methods like OnCurrentRightHandWeaponIDChange and OnIsTwoHandingWeaponChanged to handle equipment changes.

3. Player Stats Management

  • Updates player health and stamina dynamically based on changes in attributes such as vitality and endurance.

  • Integrates with a custom Player UI to reflect updated stats on the HUD.

4. Multiplayer Interaction Handling

  • Includes ServerRPCs and ClientRPCs for reliable communication between server and client for weapon actions and updates.

PlayerEquipmentManager Script Overview

This script manages the equipping and unequipping of weapons and armor in a multiplayer game environment. It handles loading models, calculating stats, and synchronizing equipment changes across clients. The script also supports a dynamic two-hand system for weapons and ensures that equipment changes are reflected visually and mechanically.

Key Features

  1. Dynamic Equipment Loading

  2. Weapon Management

  3. ​Two-Handed Weapon Support

1. Dynamic Equipment Loading

  • The script dynamically loads models for equipped weapons and armor.

  • It uses predefined slots for each equipment type (e.g., head, body, legs, hands).

2. Weapon Management

3. Two-Handed Weapon Support

  • Allows players to two-hand either their left or right weapon.

  • Updates animations, strength bonuses, and model placements based on the two-hand state.

PlayerManager Script Overview

The PlayerManager script is the central hub for managing a player character in a multiplayer game using Unity and Unity Netcode. It orchestrates interactions between various sub-managers like locomotion, inventory, equipment, and combat, ensuring seamless synchronization of player actions and states across the network.

Key Features

  1. Modular Manager System

  2. Networked State Management

  3. Multiplayer-Specific Behavior

  4. Save and Load System

  5. ​Death and Respawn Logic

1. Modular Manager System

  • The script integrates multiple sub-managers (e.g., PlayerAnimatorManager, PlayerStatsManager) for handling specific aspects of the player character, adhering to the single responsibility principle.

  • Ensures all sub-managers are properly initialized during the player's lifecycle.

2. Networked State Management

  • Synchronizes player stats, equipment, animations, and actions across all connected clients.

  • Uses OnValueChanged callbacks to handle changes in network variables and update the UI or gameplay logic accordingly.

3. Multiplayer-Specific Behavior

  • Implements ownership checks (IsOwner) to ensure only the client controlling the player can execute certain actions (e.g., movement, input).

  • Loads and synchronizes player data when joining or leaving a multiplayer session.

4. Save and Load System

  • Supports saving and loading player data (CharaterSaveData) to ensure persistence across game sessions.

  • Handles equipment, stats, and positional data, restoring the player's state accurately when rejoining.

5. Death and Respawn Logic

  • Handles player death and revival, including UI updates and network synchronization.

  • Plays death animations and resets stats on revival.

Code Challenges and Solutions

PlayerNetworkManager Challenges and Solutions Overview

1. Ensuring Smooth Synchronization Across Clients

  • Challenge: In a multiplayer environment, ensuring all clients see the same state for critical variables like player equipment, stats, and actions can be difficult due to latency and potential desynchronization.

  • Solution:

    • Leveraged Unity Netcode's NetworkVariable system to track and synchronize key player states in real-time, such as equipped weapons, armor, and spells.

    • Used change callbacks on NetworkVariables (e.g., OnCurrentRightHandWeaponIDChange) to trigger updates whenever a value changes. These updates ensure that any modification is immediately reflected across all clients.

    • Implemented logical checks to prevent redundant updates, reducing unnecessary network traffic.

Achieved seamless synchronization, ensuring all players experience consistent gameplay regardless of their connection quality.

2.Managing Complex Equipment States

  • Challenge: Tracking and managing various equipment slots (weapons, armor, spells) while allowing for real-time updates presented challenges, particularly with interdependent equipment states like two-handed weapon usage.

  • Solution:

    • Designed a modular system using NetworkVariables for each equipment type (e.g., currentRightHandWeaponID, headEquipmentID).

    • Developed specialized methods (e.g., OnIsTwoHandingWeaponChanged) to handle state transitions dynamically, including animations, effects, and stat adjustments.

    • Integrated with a centralized item database (WorldItemDatabase) to ensure consistent item instantiation and data retrieval.

Allowed for robust handling of equipment changes, improving the user experience and enabling more dynamic gameplay scenarios.

Key QA Responsibilities

The testing process for Crusade was iterative, beginning during early development and continuing through to the final stages of production. It consisted of the following key phases

link to QATrello :https://trello.com/invite/b/67858556de69c209e5a138da/ATTI8d057659152cc01bf2b1acd906925c3eD399F4BD/crusade

image.png

The testing process for Crusade was iterative, beginning during early development and continuing through to the all stages of production. It consisted of the following key phases:

  1. Unit Testing:

    • I conducted unit tests during the development of core systems, such as combat mechanics, inventory systems, and AI behaviors. This ensured that each individual feature worked as intended in isolation.

    • Automated tests were implemented for repetitive tasks, such as verifying inventory item management and NPC behavior triggers.

  2. Integration Testing:

    • After ensuring each feature functioned independently, I tested the interaction between systems, such as the inventory system working seamlessly with the combat mechanics and AI.

    • Focus was given to transitions between states, such as equipping armor or transitioning between areas within the game world.

  3. Playtesting:

    • Internal playtesting sessions were conducted to evaluate the player experience. This included testing the game's difficulty curve, the balance of combat systems, and environmental exploration.

    • I also invited external players to try the demo and gather feedback on gameplay flow, responsiveness, and immersion.

  4. Regression Testing:

    • As bugs were identified and resolved, I revisited related systems to ensure fixes did not introduce new issues or reintroduce previous ones.

Challenges In Game Development Overcome

I faced substantial challenges related to network latency and synchronization, which required an in-depth approach to guarantee a fluid multiplayer experience. Initially, there were noticeable delays that disrupted the seamless interaction between players, so I focused on optimizing data management to reduce the data load and improve performance.I enhanced the game’s responsiveness, minimized lag, and ensured that interactions felt intuitive and consistent across all player devices. This careful handling of network challenges created a more immersive and enjoyable experience, enabling players to stay engaged without interruptions or delays.

bottom of page