Native interface events are not callable by default, which differs from native interface *function* implementations.

Since we implicitly create new function graphs for non-event functions when an interface is implemented, that code path marks the function as callable by default. In other words it's not required to add 'BlueprintCallable' to the UFUNCTION() markup inside the native interface class header file.

Whereas dropping an interface event node into the Event Graph in order to implement it does not implicitly mark it as callable, and thus the user is required to add 'BlueprintCallable' to the UFUNCTION() markup in that case.

In addition, for interfaces created in the editor (i.e. non-native), all functions appear to be callable by default. So there's a minor inconsistency there that could lead to some confusion with native interfaces. Perhaps to be consistent with non-interface native functions, we should not implicitly make native interface function graphs callable by default? And thus require 'BlueprintCallable' for all native interface functions?

Fix UE-51650

"Session Disconnected" UEFN

Delay nodes occasionally don't fire the "Completed" output in a nativized build

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

My map looks so rigged because part of the skybox is missing it says "Your scene contains a skydome mesh with a sky material but it does not cover that part of the screen

I am not able to find world outliner how to enable it?

Installer 4.10 failed with error code R-1603

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

Teleporter in the Creative Hub is Locked and cannot be accessed

An error occurred while trying to generate project files !?