Introduction and Architecture

</aside>

The Multiplayer Health System (MHS) is a modular framework developed under a Component Architecture to manage survival attributes, damage processing, and replication states in Unreal Engine 5.

Its design prioritizes Total Decoupling: the system has no direct dependencies on base classes like Character or Pawn, allowing for universal integration into any actor requiring destruction logic.

1. Implementation Versatility

</aside>

The system automatically adapts its logical behavior based on the actor's context configuration:

<aside>

Characters (Complex): Enables advanced mechanics such as Downed states (DBNO), Ragdoll physics, directional impact animations, and cooperative reanimation.
Vehicles & Machinery: Manages structural integrity and shielding systems (Shield) without executing humanoid animation logic.
Props & Objects: Can be integrated into static elements (explosive barrels, barricades, turrets) to grant them vital attributes and destruction events. </aside>

2. The Core: BPC_Health_System

</aside>

All functional logic is encapsulated within the Actor Component 🟦 BPC_Health_System. Integration is "Plug-and-Play"; by adding this component, the actor acquires:

<aside>

Attribute Management: Automatically replicated Health and Shield bars.
Damage Processing: Native listener for Event AnyDamage with layered absorption calculation (Shield > Health).
Life Cycle: State machine for regeneration, death, and respawn. </aside>

3. Survival Logic (Absorption)

</aside>

The system manages actor durability using a hierarchical protection layer system:

<aside>

Shield Priority (Shield Gating): The shield acts as an absolute barrier. It absorbs 100% of incoming damage before Health is affected.
Damage Overflow: If the received damage exceeds the current shield amount, the system breaks the shield and mathematically applies the remaining damage (Overflow) to the Health bar in the same frame. </aside>

4. Identity & Teams (BPI_Target)

</aside>

To manage entity identification and validate Friendly Fire without expensive casting, the system uses the interface 🟨 BPI_Target:

<aside>

Actor Type (Enum): Uses ENU_Actor_Type to define the entity's physical profile (Character, Vehicle, Turret, Object). This allows the UI system to adapt the type of Health Bar displayed.
Team ID (Enum): Uses ENU_Target_Type to define faction affiliation (Ally, Enemy, Neutral). Critical for the system to filter allied damage.
Actor Name (Name): Provides the visual name for the Overhead Widget. </aside>

5. Testing Environment (Basic AI)

</aside>

The system includes an autonomous Demo AI to validate damage and team mechanics.

<aside>

Behavior: Visually detects enemies, initiates combat, and fires elemental damage projectiles.
Reset Cycle: Upon elimination, they execute physics logic (Ragdoll) and automatically reappear (Auto-Respawn) to allow for continuous testing. </aside>

DMD HANGAR

</aside>

PROJECT REQUIREMENTS

</aside>

Introduction and Architecture

1. Implementation Versatility

2. The Core: BPC_Health_System

3. Survival Logic (Absorption)

4. Identity & Teams (BPI_Target)

5. Testing Environment (Basic AI)

Previous Page

Next Page