Actor-Pointer-UPROPERTY

[anonymous_user_82a61a3e]

@kamrann;303624

You could have your characters derive from a base class or blueprint, which in its BeginPlay event found the actor which should be used as the default (perhaps by searching for actors of a specified class) and assigned it to the property. Perhaps you should also consider spawning your characters through code/blueprint rather than placing them in your level. This approach is generally more scalable when it comes to wanting to create new levels. If you do it this way, you can set up the default references using some heuristic as you spawn them.

Yes, that would be a clean way I guess. I also thought about having two properties - one is the default-blueprint - and the other the instance.

The instance-property could be assigned in the construction-script by finding instances of the blueprint.

But I must admit, that I do not really see the point in disallowing editing instances in blueprints, since I would “left that to the implementator”.
This is mainly because I think the above workflow is more complicated than it could be… because “it is only one property…” ? :

Really nothing critical…