On the contrary, a legit one. There were great plans on how the Child Actors Components could work but it seems they stopped working on it:
Nesting Blueprints - intended workflows?
- At the moment, the only mechanism available for ‘nesting’ Blueprints is the child actor component. This isn’t really nesting in the way most people would want, but rather it ties the lifetime and positions together, but they are technically independent actors. We’d like to improve the way that blueprints can be nested, but it’s currently not on the roadmap.
State of Child Actors?
- Not used heavily in terms of scaling to 1000s of things, but we do use it wherever it makes sense
- Supply drops, balloon and crate are separate actors with child actor comp
- We’d like to have fully nested hierarchy, child actor components are just what we have today
- If all you need is the transform, there are some other tools
- On any vector/transform property, can mark to show a 3D widget
- If just attaching things in level and not BP editor, you can use sockets
You can blueprint the desired behaviour but it would be N.I.C.E. to have the variables and components (and their variables as well!) exposed to the World Outliner… 