This skill helps an agent build Unreal Engine 5.8 Niagara effects that gameplay can spawn, drive and clean up, and that keep rendering where the camera looks. It covers exposing User parameters, ordering modules, choosing CPU or GPU simulation, and spawning one-shots and attached effects from C++ or Blueprints.
It also lists the usual problems: parameters that do nothing, components that crash on a null return, effects that vanish at the screen edge because of bounds, and looping effects that never stop.
What You Get
- A workflow covering the Niagara module in Build.cs, parameters, module order and sim target choice
- A C++ pattern for a pooled one-shot impact and an attached looping effect driven by User parameters
- Verification steps with a functional test run offscreen and Niagara console commands for the debug HUD and cost
- A gotcha list for null spawn results, bounds, pooling, GPU read-back and Cascade tutorials
- Version notes on what changed in UE 5.8 and the 5.9 Preview
Common Use Cases
- Spawning muzzle flashes and impacts from C++ with pooling
- Driving a fire or aura effect from gameplay values through User parameters
- Debugging an effect that does not appear or disappears when its origin leaves the screen
- Finding leaked components from looping effects that were never deactivated
What Makes It Unique
The skill separates what gameplay may change (the User namespace) from internal sim values, and it ties pooling method to who keeps the component pointer. It notes that Niagara needs a renderer in headless tests, so the offscreen option is used there. Shader authoring, hit-stop and audio go to sibling skills.
Under The Hood
The agent loads the SKILL.md only; it has no reference files. It greps your Source and assets, writes C++ that calls the Niagara function library, adds the Niagara module to Build.cs, and runs shell commands: the engine build script, the editor command line for asset validation and a headless functional test with an offscreen renderer. It does not fetch web pages itself. Some checks ask you to run the game and report what the Niagara debugger shows.