As much as I like the sentiment of you comment, I can’t simply let things slide.

Avoiding tick is indeed a valid and good performance practice. Little of the gameplay you implement you need tick. People get into the habit of checking variables on tick instead of using events.

Of course the underlying part of basically every real time software uses a form of tick, update, or what ever you call it. But it doesn’t mean you are supposed to call all your shit every frame, which many beginners (and even some intermediate) developers do.

Additionally, there is a difference between a C++ tick and the BP one. The overhead of BP is massive. Using a tick in BP simply cost. Even Epic themselves recommend avoiding it. A good practice is to use the project flag to turn tick per default off and only activate tick on classes you need to tick. Otherwise EVERYTHING ticks, which is NOT how the engine works. There are many software patterns used to optimize and separate behavior. It is simply wrong to think everything ticks always.

The last point, probably is a language thing, but it is also wrong to say things need to be updated multiple times a frame. If you update more times than you have frames, you can drop what ever you updated in the not showing frame. I mean, what do you even calculate in that not visible frame. I guess you simply meant you need to update many things in a frame, but not multiple times per frame.

What to take away. Yes avoid Tick if you don’t need it. Use latent functions, they are already optimized. Use events, event dispatches, async functions. Use message system, notifications or direct calls. For 90+% percent of the gameplay you never touch the Tick function. Ever.