<aside> <img src="/icons/key-antique_gray.svg" alt="/icons/key-antique_gray.svg" width="40px" />

• TECHNICAL LEGEND </aside>

• NAVEGATION

  DAMAGE AND VISUALS

<aside> <img src="/icons/triangle-alternate_gray.svg" alt="/icons/triangle-alternate_gray.svg" width="40px" />

Damage Logic and Visuals

</aside>

The MHS utilizes a Data-Driven architecture to manage visual feedback. This approach decouples programming logic from artistic design, centralizing visual configuration within a single Data Table.

<aside> <img src="/icons/triangle_lightgray.svg" alt="/icons/triangle_lightgray.svg" width="40px" />

1. Visual Centralization (DT_Visual_Data)

</aside>

The entire visual identity of the system resides in a master Data Table.

<aside>

Asset: 🟦 DT_Visual_Data.

• Function: Links an Element (Physical, Fire, Electric, etc.) to its graphic attributes:
  • Color: Defines the color palette associated with the element.
  • Icon: The representative image of the element displayed in the User Interface (UI).
  • Text (Typography): The Font Family that floating damage numbers will use. </aside>

When the system processes damage, it queries this table to render the result on screen, avoiding the use of static values or direct dependencies within Blueprints.

<aside> <img src="/icons/triangle_lightgray.svg" alt="/icons/triangle_lightgray.svg" width="40px" />

2. Floating Damage System

</aside>

To display damage amounts, the system does not use simple screen widgets but rather physical actors for better depth management and occlusion.

<aside>

• Actor: 🟦 BP_Floating_Damage. The actor spawned in the world at the impact location.
• Widget: 🟦 WBP_Damage_Billboard. The interface component contained within the actor, responsible for rendering the number with the correct typography and color. </aside>

<aside> <img src="/icons/triangle_lightgray.svg" alt="/icons/triangle_lightgray.svg" width="40px" />

3. Color Logic & Feedback

</aside>

Upon receiving an impact, the system triggers visual responses that follow different logic for Particles vs. Numbers:

<aside>

A. Particles (Health Context)

Particle systems (Niagara/Cascade) react to the Actor State or the layer receiving damage:

• 🔵 Blue: Impact on Shield.
• 🔴 Red: Impact on Health.
• 🟣 Purple: Actor is Immune.
• ⚪ White: Attack has been evaded (Miss). </aside>

<aside>

B. Floating Numbers (Elemental Context)

In the Standard state, the number's color does not depend on whether it hit health or shield, but on the attack's Element defined in DT_Visual_Data.

• Example: A fire attack will show orange numbers, and an electrical attack will show Yellow numbers, regardless of whether they hit health or shield.
• Exception: The Immune and Miss states override this logic to display their specific state colors and texts. </aside>

<aside> <img src="/icons/triangle_lightgray.svg" alt="/icons/triangle_lightgray.svg" width="40px" />

4. Impact States (Status_Type)

</aside>

Logical behavior upon impact is defined via the enum variable 🟩 Status_Type:

<aside>

• Standard: Normal damage processing. Absorption rules apply, and the element's color is shown. </aside>

<aside>

• Immune: Temporary invulnerability.
  • Logic: Damage is nullified (0).
  • Feedback: Displays immunity text and purple particles. </aside>

<aside>

• Miss: Evasion.
  • Logic: The impact is ignored.
  • Feedback: Displays miss text and white particles. </aside>

<aside> <img src="/icons/triangle_lightgray.svg" alt="/icons/triangle_lightgray.svg" width="40px" />

5. Weak Points

</aside>

For critical zone detection, the system uses a modular approach.

<aside>

Component: 🟦 BP_Weak_Point (Child Actor).

• Configuration: The child actor's Box Collision is aligned with the vulnerable bone (e.g., Head).
• Communication: Via the interface 🟨 BPI_Impact, the attacker notifies the impact position and power. If it matches the Weak Point collision, the critical multiplier defined by the weapon is applied, altering the final value processed by the health system. </aside>