Xae Game Systems - Modular Weapon Trails Pro

Quick Start Video : https://www.youtube.com/watch?v=AnQDLdtyico

Elemental weapon trails drawn from your real attack animations: one Anim Notify State, no code.


Open an attack montage, add the ANS_WeaponTrailPro notify state over the swing and press Play. That is the whole setup. The trail is the real surface your blade sweeps through, including every turn of the wrist, character rotation and root motion, and it fades out on its own. The weapon held by the character is found automatically, so a default Steel trail works before you change a single setting. Then pick one of eleven elements from a dropdown.


The shape of the trail and its element are chosen separately: any of the 12 shapes works with any of the 11 elements. Change one attack with Customize This Attack, or duplicate a preset and make your own.


It works with any character and any Static Mesh or Skeletal Mesh weapon: no component to add, no base class, no Animation Blueprint changes, no GAS. Visual only: it never applies damage or hit detection.


FEATURES

- One Anim Notify State is the whole workflow, on any montage or animation sequence

- Real two-edge geometry from the weapon's actual movement, with curved in-between sections for fast swings and low frame rates

- 11 element presets: Steel, Flame, Earth, Ice, Water, Lightning, Wind, Shadow, Poison, Holy, Arcane

- 12 trail shapes: Ribbon, Tapered Slash, Crescent Arc, Flame Tongues, Jagged Slash, Crystal Shards, Fluid Wave, Twin Arc, Spiral, Lightning Branch, Shattered, Energy Blade

- Up to 6 layers per trail, each with its own shape, material, colors, width, lifetime and delay

- Speed response: faster swings can get wider, brighter and more intense

- Optional Niagara particles per element, with budgets

- The blade is found automatically; sockets, bones, local offsets or Blade Coverage for exact edges

- Weapon sources: attached weapon, the character mesh itself (fists, claws, built-in weapons), a tagged component, or set from Blueprint

- Customize This Attack: per-notify overrides without a new preset; Intensity as a single strength control

- Data-driven presets (Data Assets): duplicate one and edit it, no code

- Bring your own material through a documented parameter contract

- Hit-stop support: the trail freezes with its character's Custom Time Dilation and continues afterwards

- Safe with many characters playing the same montage, repeated attacks and interrupted montages

- Clear on-screen setup messages with the fix, never a silent guess (not shown in Shipping builds)

- Blueprint and C++ API without animations: Start Weapon Trail, Stop Weapon Trail and more

- Quality levels and per-world limits; trails are removed after they fade

- Works next to Modular Weapon Trails Lite (no shared classes); migration guide included

- Full, documented C++ source


INCLUDED

- Runtime code plugin with full C++ source

- ANS_WeaponTrailPro notify state, trail subsystem and Blueprint function library

- 11 presets (Data Assets), 5 materials with one material instance per preset layer, 3 material functions, 6 textures, 11 Niagara assets

- Demo level (Demo > Maps > L_WeaponTrailsPro_Demo): 52 characters in eight stations (weapons, elements, shapes, combinations, layers, speed response, Blueprint control, many characters)

- 12 guides, from Quick Start to Troubleshooting, plus Performance, Compatibility Matrix and Changelog


TECHNICAL DETAILS


Modules: ModularWeaponTrailsPro (Runtime)


C++ classes: 6 (UCLASS), 12 structs (USTRUCT), 6 enums


Dependencies: engine modules and the engine's Niagara plugin (enabled automatically). No third-party plugins, GAS or Enhanced Input required.


Platform: Windows (Win64)


Engine versions: 5.4, 5.5, 5.6, 5.7, 5.8


Networking: visual only. Notifies run on every machine that plays the animation, so each client draws its own trail; dedicated servers create nothing. No replication code.


Performance: measured numbers and the limits are in Docs/Performance.md and Docs/9_PerformanceAndScalability.md.


Not supported in 1.0: first-person view models (weapons only the owner sees).


Most presets are additive and look best against darker backgrounds.


Code plugin: use "Install to Engine" in your Fab library, then enable it per project in Edit > Plugins. Works in Blueprint and C++ projects; no C++ writing needed. Plugin content appears in the Content Browser under Plugins (enable Show Plugin Content).


DOCUMENTATION

Included in the plugin's Docs folder (start with 1_QuickStart.md).


SUPPORT

■■■.mustafa96@gmail.com