Blueprint Node: "Event Tick"

The Event Tick node is the node that you should NOT touch it and avoid it at any cost !

The legendary Epic Games staff Zak Parrish says:

" I try to tell artists and people who are not skilled scripters to never use Tick. Just don't look at it, don't touch it, pretend it's not there, and even if you think you need it and if you're sure you need it - STILL DON'T USE IT !"

​

Watch his video here ( 31:00 ).

​

Why is this Blueprint so bad?

- It's because the Event Tick is ticking every second based on your machine's Frames Per Second ( FPS ).

For example, if you have a great PC / Laptop configuration and you can run your game on 120fps, when you connect a node to the Event Tick that node will run continuously for 120 times per second !

​

Now Imagine you have a node that is "heavy" on your RAM memory for example, and you connect that node to the Event Tick, and you play your game for 60 minutes ?

​

Let's calculate and see the outcome:

- You play your game for 60 minutes

- That's equal to 3600 seconds

- Event Tick is ticking 120 times per second

- 3600 seconds x 120 = 432.000 ticks in 60mins !

Quite a number isn't it ?

​

Summary:

- Avoid using Event Tick node at any cost !

Use alternative nodes instead. If you need help with this node feel free to discuss with our team.