Subscribe to download
Clocking - Always vs Every (Runtime vs Timer)

This example is used to study differences between using Always and Every (Runtime vs Timer). You can see how the changes effect your application and test out examples. With this knowledge you can appropriately apply events.

I also noticed that when you move the frames around, everything pauses... but the Every Stress Test makes up lost time (if paused for 3 seconds, 3 objects appear immediately). The Always Stress Test just continues where it was left off. The oddity is that the Timer Using Every 50 is not in sync with the Every Stress Test (it does not play catch up). I believe the oddity is due to how the events are handled and the Every Stress Test keeps adding, but the Timer Using Every 50 has 2 events that intermingle. I have not pinpoint the difference yet since I tested changing the clock to Every 1000 and 1 event which did not change the oddity.

Discussion where this example was created:
https://steamhost.cn/steamcommunity_com/app/248170/discussions/0/527273789693229431/
Note: The examples in the discussion that are not workshop were done incorrectly.

This Concept is expanded upon with this new workshop item:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=794973882