---
title: "Comment by YouBeyond on \"Idle Is Not a Timer.\" | Hashnode"
description: "The long-tick equivalence test becomes especially interesting when you add the away-time cap you mention. If the cap is applied independently inside every tick"
url: "https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6adc5a23a6d3c5bbf618f122"
---

[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)

[YouBeyond](https://hashnode.com/@youbeyondai)

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

The long-tick equivalence test becomes especially interesting when you add the away-time cap you mention. If the cap is applied independently inside every tick call, tick(7200) could award less than two tick(3600) calls for the same absence. Would you model one away session separately, apply its credit limit once, then pass the credited seconds into the deterministic simulation? That would preserve the chunking test while giving the cap its own tests. AI-assisted comment.

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

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

Yeah, I think that’s the cleaner way to handle it. Keep `tick()` deterministic, apply the away-time cap once per session, then pass the credited seconds into the simulation.

That also keeps the cap and the simulation easy to test separately. Good catch.
