In this lesson, you will learn how to create "BlueprintPure" functions to make your Blueprint graphs cleaner and more efficient by eliminating unnecessary execution pins.
Why Do We Need BlueprintPure?
When you define a standard BlueprintCallable function, Unreal adds a white execution pin to the node. This forces the node to be triggered by the flow of your code (the "white wires"). However, if you are simply fetching a piece of data—like a character's current health or a calculated value—you don't need to "fire" the node. You just need the value to be available for use.
By using the BlueprintPure specifier, we strip away the execution pins. This tells Unreal that your function has no "side effects"—it doesn't change the game state or modify variables. It simply performs a calculation or returns a data reference.
Implementing a Pure Function
To implement this, you add BlueprintPure to your UFUNCTION macro. A common best practice is to also include BlueprintCallable so the system understands it is exposed, and Category to keep your editor organized.
UFUNCTION(BlueprintPure, Category = "Gameplay|Stats")
float GetNormalizedHealth() const;
When you use this in the Blueprint editor, the node will have no white pins. You can simply drag a wire from the output pin into any other node that requires a float.
Why This Optimizes Data Flow
Using BlueprintPure significantly cleans up your Blueprint graphs. Instead of snaking white execution wires across your entire Event Graph just to fetch a variable, you can place these getter nodes exactly where they are needed. Because the function is marked as "Pure," the compiler knows it can evaluate this node every time it is requested without worrying about triggering a chain reaction of logic. This leads to code that is not only easier to read but less prone to "spaghetti" wire layouts.
Key Takeaway: Use BlueprintPure for functions that only read data without modifying the state of your game, allowing for cleaner, wire-free data retrieval in your Blueprints.