Hi everyone,
I noticed that a standard C++ virtual function marked with UFUNCTION(BlueprintCallable) actually shows up in the Blueprint “Override” dropdown and can be overridden in Blueprints.
This made me wonder: if a regular virtual + BlueprintCallable function already allows Blueprint overrides, what is the exact technical reason to use BlueprintNativeEvent instead?
Specifically, I’d like to clarify:
- Are there differences in behavior when the function is called from C++ vs. Blueprint (e.g., whether C++ calls properly trigger the Blueprint override)?
- Are there any hidden caveats, reflection issues, or performance differences between the two approaches?
Any official clarification or insight on how UHT handles these two under the hood would be greatly appreciated. Thanks!
5.8.4