Best Practices
This document provides a few pointers on how to get the most out of the Reactional Plugin in Unreal. It is not a complete guide but rather a collection of tips and tricks.
Summary
Version Support
- Unreal Engine 5.4
- Unreal Engine 5.3
Considerations
When working in Unreal, the Reactional API is made to be easy to use and prototype with. Depending on the size of your project and the complexity of the logic, consider this:
Simple Logic, BP_PlyerClass or just a Few Reactional dependent Actors in the Level
When using the Reactional API to react to gameplay, whether the thing reacting is a BP_PlayerClass, or a few actor instances in the level , and / or if they are dependent on simple conditions , you can drive your logic locally in any Blueprints without significant impact on performance.
Big projects, lots of Actors and complex logic
When using the Reactional API to drive complex behaviors of the gameplay, or using the same logic on multiple actors in a level , consider the consistency, scalability, and maintainability aspects. Centralizing Reactional logic into a manager could help to manage your performance costs.
Performing logic calculations in a centralized manager reduces computational overhead by avoiding redundant calculations in each actor's blueprint. This significantly improves performance, especially in complex scenes with many actors, or actor duplicates like pickups or other scene elements that are dependent on Reactional.
Other Tips & Tricks
Some other helpful tips and tricks
-
Heavy functions as LoadBundle should in most cases be called in Async mode.
-
Using Parameter Collections is a great way to communicate in Unreal from Reactional Logic to VFX and Materials to set the scalar or or vector parameters.
Build Support
- Windows
- Mac
Coming Soon
- iOS
- Android
Reactional Integration
- Metasounds: Reactional works with Metasound Graphs and its Nodes via the Reactional Event Triggers and Rendering Output. Check out the Metasound API section for more information