- Do not create a new blueprint component via the Subobject Data subsystem if the given class is not a blueprint type.
- Check for existing classes with that have the same name when creating a BP class to prevent the user from creating invalid packages.
- Add logging to show the user a reason for failure when the given class name is invalid.
#rb phillip.kavan
#jira UE-116746
#jira UE-116749
#jira UE-117000
#preflight 60b8e5f78e7ee10001f44220
[CL 16549867 by ben hoffman in ue5-main branch]
Correctly sort non-scene components to the bottom of the component tree.
This is some logic that was missed during the SCS editor refactor and is known to work already.
#jira UE-115776
#rb trivial
#rnx
#preflight 60a40b42292e32000148e10b
[CL 16374996 by ben hoffman in ue5-main branch]
The SubobjectDataSubsystem is how users can manipulate a given object within Blueprints or Python scripting. Given a Uobject instance in a level or a UBlueprint asset, you can use GatherSubobjectData to get get an array of handles that you can use to manipulate that subobject.
This is what the new SubobjectEditor (Previously the SCS editor) will be using instead of having all its logic within slate code.
#rb marc.audy
#jira UE-64131
#preflight 6082ce4f8de3a60001cf6af8
#preflight 6082d84a92d7e700019f53e0
[CL 16104548 by ben hoffman in ue5-main branch]
