Throttle and Debounce

The plugin provides access to two special conditions: Not more than once in <X> seconds and On a deferred event.

If you prefer JavaScript, you can refer to the articles: Debounce example with a search form and Throttle example with page updates on scroll.

Throttle

Sometimes a part of the game can significantly affect performance. For example, physics or artificial intelligence processing.

Due to the complexity of such computations, it is better to avoid using them too often. For such cases, Every <X> seconds is usually used to run code once in a while, but this is not always possible.

For example, we have some complex game mechanic that runs when the screen is tapped. In situations like this, when you need to limit the frequency of code execution but cannot use a timer, you can use a special Not more than once in <X> seconds condition.

Debounce

Some Yandex Games SDK methods have a limit on the number of requests in a certain period of time. If you neglect these limits, your game may fail moderation.

For example, if you update the leaderboard score too often, you should use a special On a deferred event condition together with the trigger condition Delay execution. This combination works similarly to the native Signal → On signal combination, but delays the call for a certain time since the last execution attempt.

However, it can be confused with the previous Not more than once in <X> seconds condition, because we also used it to hide code that should not be called too often.

The main difference is that Not more than once in <X> seconds limits the call frequency, while On a deferred event delays the function call for a certain time. This is exactly what we need, because we do not necessarily need to run the function too often, we just need to stay within the limit.

Visualization of the difference between Not more than once in <X> seconds and On a deferred event:

---

Repository