[Plugin] Object Pool Component

[Kelheor]

@XaVIeR;713720

I have remade this plugin for around 10x; the reason I endup with this architecture is because the way Unreal works. Pooling ordinary AActors wasn’t giving any noticeable performance boosts, I had to introduce intermediate C++ Classes to make performance work the way I was expecting it to be…
By the way, you lose absolutely zero workflow when re-parenting your base class to APooledActor instead of AActor, there’s no drawbacks in doing so; the plugin provides a custom Spawner node and C++ functions exactly to cover such a case, you can spawn any actor that is a child of APooledActor there.

There are some reasons against re-parenting. What if in future I’ll decide to not use this plugin for some reasons? What if I have hundreds of actors, which I need to re-parent? What if I decide to re-use these actors in another project, where I can’t use your plugin? etc… Of course, all of these issues can be solved, but it will require additional time and efforts. Your PooledActor derived from AActor anyway, so I wonder did you tried to add ChildActorComponent to it and test performance? I assume it shouldn’t affect performance, because otherwise even if you reparent existing actor to pooled actor if it has heavy components (like ChildActorComponent, because it’s also possible) in it, these components will remove all benefits of pool in case if they won’t stored within an actor in the pool.