---
title: "Comment by Abhinav Sharma on \"Idle Is Not a Timer.\" | Hashnode"
description: "Time as a plain tick count is what makes the whole design testable - an hour away becomes game.tick(3600) and the suite never waits on a clock. It is the same r"
url: "https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6adbcb85b7a32220bb790348"
---

[Discussion](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)

Comment [Idle Is Not a Timer.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 23](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6adbcb85b7a32220bb790348)

Time as a plain tick count is what makes the whole design testable - an hour away becomes game.tick(3600) and the suite never waits on a clock. It is the same reason engines separate the simulation step from render frames: determinism in the core, wall time only at the edges.

[Mikey Nichols](https://hashnode.com/@mNix)

[Oct 24](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6adbcb85b7a32220bb790348#reply-6adc4945b78c78953a30b7c0)

Exactly! That separation ended up being one of my favorite parts of this step.

I started from the much smaller problem of “how do I test an hour away without waiting an hour?” and `game.tick(3600)` fell out of that. But it also creates that nice boundary you described: whatever is running the game can measure wall time, while the Rust side only has to care about what that amount of elapsed time means for the game state.

I like the comparison to separating simulation from render frames too. That is pretty much where this series is heading next — pulling the game rules away from the environment that happens to be running them.
