Spawning a Blueprint *outside* of the Constructor in C++ (Version 4.1.1)

[anonymous_user_4fe9f58b1 (anonymous_user_4fe9f58b)]

@TTaM;225691

From what I understand, UBlueprint objects do not get added to the Shipping build type. Therein, this code will fail. To fix it, replace the last ’ on the asset ref with _C’ and change UBlueprint to UClass. And the generatedclass bit.

They do, but that’s bound to change.

I went ahead and corrected the wiki articles I could find that still directly refer to UBlueprint GeneratedClasses. That only leaves the forums, hopefully people will catch on and stop repeating this approach before it gets deprecated in a breaking fashion.

@sirfaty;93979

“MyBlueprint_C” is the name of the blueprint-generated class inside the “MyBlueprint.uasset” package. You don’t need to specify the type in the asset reference anymore.

As far as I can tell, it was never necessary. It gets ignored with barely a warning, it’s only there if you want to identify your asset type at a glance from its path.

Also, for classes, there is a separate constructor helper which can help in returning strongly typed subclasses:

static ConstructorHelpers::FClassFinder<AMyBlueprintBase> MyBlueprintClass(TEXT("/Game/Path/To/MyBlueprint.MyBlueprint_C"));

if (MyBlueprintClass.Class)
{
	MyCharacterReference = MyBlueprintClass.Class;
}

Both approaches work equally anyhow.