Yes, exactly this for me.
Hello from the future (Unreal engine 5.7),
I’ve had a similar problem and this thread is the closest to my original problem so I hope this can help anyone with the same or similar problem to mine.
The scenario goes like this: I am making a component that is responsible for a system separated from its actor so that it can just be added to any actor and act exactly the same. In order to do its job properly this component needs to spawn additional components in the owner actor. To manage those components this original component also has to be able to delete them so that functionality is completely contained within the original component without actor having to implement any interface functions etc.
The Destroy Component node itself gives this explanation:
… This may not be used to destroy a component that is owned by an actor unless the owning actor is calling the function.
This would lead you to believe that you cannot call the destruction of any component unless you do it inside the actor itself. However if you have a reference to the actor (with node Get Owner) you can drag of its output (Return Value) and search for Destroy Component node. Be sure to turn !!! CONTEXT SENSITIVITY OFF !!! This will give you a slightly modified node that has two inputs. One for the component you want to destroy (as with the usual Destroy Component node; Target) and another one that requires an actor that is calling that functionality (Object).
Hope this helps. I have no idea why this is so hidden…
