Sorry I’m going to beat this horse to death right quick. If I have an object-pool that has “Instantiate on Demand” checked it will spawn unpooled objects (still of type pool because that’s the base class of such objects) whenever there’s no free objects in the pool. Later when I want to clean up such objects with “Return to Pool” nothing will happen because it didn’t come from the object-pool. That was what I meant by orphaned. I just think that an object should be destroyed if it has no owning pool. I can manually check for this myself but I think it’s cleaner if at least there was a parameter on “Return to Pool” to destroy an object if it’s found to have no owning pool. Just my two cents, but thanks for the plugin. It solved a hitch I was having in my infinite runner. Really useful for me. I was actually surprised to find there was nothing like this built-in to the engine.