Blueprint Optimisation Guidelines
Reduce Unnecessary Function Calls:
Avoid excessive function calls by consolidating similar actions.
Minimize event trigger frequency to prevent unnecessary executions.
Optimise Loops
Use 'For Each Loop' instead of 'For Loop' whenever possible.
Batch operations to reduce the number of loop iterations.
Minimise Redundant Computations
Cache frequently used values to avoid redundant calculations.
Use Blueprint Variables for intermediate results in complex operations.
Use Switches Wisely:
Prefer using 'Switch on Enum' or 'Switch on Int' instead of multiple branches.
Conditional Checks:
Organise conditions from most common to least common to improve efficiency.
Use 'Gate' nodes to selectively enable/disable sections of logic.
Optimise Event Handling:
Use Replication Sparingly
Avoid unnecessary replication of variables across the network.
Minimize Graph Complexity
Split complex Blueprints into smaller functions for better readability and maintainability.
Blueprint Profiling
Use the 'Performance Profiler Tool' to identify performance bottlenecks.
Memory Management
Release resources using 'Release Dynamic Object' to prevent memory leaks.
Reduce Node Count
Split complex Blueprints into modular functions to manage node count.
Testing and Iteration
Regularly test and profile Blueprints to verify optimisations.
Remember, optimisation should be based on specific project requirements and performance testing. Strive to find a balance between readability and performance while following these guidelines. VerseX will approve all blueprints before implementing them to the VerseX world to ensure that there are no malicious and heavy codes.
Last updated