---
title: "Mikey Nichols (@mNix) | Hashnode"
description: "Web Developer. Read the latest articles by Mikey Nichols on Hashnode."
url: "https://hashnode.com/@mNix"
---

@mNix

# Mikey Nichols

@mNix · West Virginia · Joined March 2024

Web Developer

[Website](https://mnix.dev/)

## Comments

[Thanks for commenting! I’m happy that it resonated =) I think having that short-tick vs long-tick test is going to save me later too.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6addb08303f6b5700ad9ce22#reply-6adde2a15089f809a540d067)

Reply · Article · Oct 25 · [Idle Is Not a Timer.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)

[That’s a really good test case. It hits the exact boundary resolve\_hit() is supposed to unify, instead of testing clicks and ticks separately. A click leaving the slime at 1 HP, then a one-second tick finishing it, would be a nice guard against missed transitions or double rewards as this grows. I’m probably adding that one.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6add124e838a42a2d61b85be#reply-6add3eb4ab6b68458e938229)

Reply · Article · Oct 24 · [Idle Is Not a Timer.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)

[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.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6adc5a23a6d3c5bbf618f122#reply-6adc90dbe793b4d3c46079c5)

Reply · Article · Oct 24 · [Idle Is Not a Timer.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)

[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.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6adbcb85b7a32220bb790348#reply-6adc4945b78c78953a30b7c0)

Reply · Article · Oct 24 · [Idle Is Not a Timer.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)
