📂 Project Structure

Overview

The ImpactFX framework has been meticulously organized following the official Epic Games Naming Conventions (Allar's Style Guide). The folder hierarchy is designed to be highly modular, allowing developers to easily locate, modify, or extend the assets without breaking references.

The project is divided into two primary root folders: Core (the actual framework) and Demo (showcase content).

Migration & Integration Note

💡 Best Practice: When migrating ImpactFX to your own project, you only need to migrate the ImpactFX/Core folder. The Demo folder is strictly for showcase purposes and is not required for the system to function in your game.

Directory Breakdown

Below is a detailed breakdown of the ImpactFX/Core directory and what each sub-folder contains:

🔵 Blueprints

This folder contains the brain of the ImpactFX framework. It houses the data-driven architecture and logic components.

• Actors: Contains the physical Decal Actors spawned in the world (e.g., BP_GroundDecal).
• Components: Contains BPC_ImpactFX, the primary Actor Component that you will attach to your weapons, projectiles, or characters to handle the impact logic.
• Data: The core of the data-driven setup. Contains the Structs (S_ImpactFX_Data), Enumerators (E_ImpactFX_Caliber), and the primary Data Assets (PDA_ImpactFX_Template) that link Physical Materials to their respective visuals.
• FunctionLibrary: Contains BP_DecalLibrary, a function used to organize and set GroundDecals.

🟢 Materials