“you can have one public actor in the level that does that”
- That does what? I’m not entirely sure what you are referring to here.
Spawning single components at runtime is easy as long as they they aren’t expected to also have child components.
With an actor, you have a viewport and component list where you can easily add additional components under the root component. Where an actor is spawned in the world, the root components are automatically created and attached. I need to create a component that has child components that can be created at runtime and attached to any actor of my choosing.
Now, I could use BeginPlay on a component blueprint to spawn it’s child components and set all my values. Or I can create an actor and just attach it as a child actor component. I want to avoid creating actors that aren’t needed but using BeginPlay and setting all values will be very tedious. So that leaves me with either a very tedious process or process that adds unnecessary overhead.
EDIT:
“…I can create an actor and just attach it as a child actor component…”
but because I don’t actually need the actor at this point, I might as well transfer the component to the desired actor, still adding unwanted overhead.