Logic after destroy

Development Programming & Scripting Blueprint
, , , ,
1

Look at the following example:

Foo(); // non-latent method
Destroy();
Bar(); // non-latent method

Destroy waits till the end of the current frame so the object is not going to be freed when Bar is called. Suppose that it doesn’t matter that the object is marked PendingKill or may be instead, object being marked is beneficial, are there any pitfalls to doing this besides bad coding style?

2

You can try to override BeginDestroy for that.

3

I updated the question to be more specific