---
title: "Comment by Mahdi Jabinpour on \"Idle Is Not a Timer.\" | Hashnode"
description: "Pulling resolve_hit into one shared transition is the most useful refactor in this step. I would add a mixed-input test where a click leaves an enemy one idle h"
url: "https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6add124e838a42a2d61b85be"
---

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

[Mahdi Jabinpour](https://hashnode.com/@mahdi-lumowp)

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

Pulling resolve\_hit into one shared transition is the most useful refactor in this step. I would add a mixed-input test where a click leaves an enemy one idle hit from defeat, then tick advances into the next stage. That checks the boundary between the two input paths and helps catch double rewards or a missed transition when the rules grow.

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

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

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.
