# The 0.6-second tick: how input queueing actually works

What a game tick is in OSRS, how many ticks there are per second and per minute, and exactly which tick your click lands on. With a metronome to click along to.

By Jonah. Published 5 Oct 2026. Last checked 4 Oct 2026 against sim 1.0.0. Canonical page: https://microgrind.io/guides/game-tick/

If you play Old School RuneScape you will hear "tick" constantly: tick-perfect, 1-tick flicks, 3-ticking. It all comes back to one idea. The game world does not update continuously. It moves forward in fixed steps, and everything you do is fitted into those steps. Once the step is clear, most "tick-perfect" techniques stop being mysterious and become a matter of counting.

## What is a game tick?

A tick is one step of the game's clock. The OSRS Wiki gives the standard length as **0.6 seconds**, and describes actions you make during a tick as starting by the beginning of the next one ([Game tick, OSRS Wiki](https://oldschool.runescape.wiki/w/Game_tick)). Between two ticks the game state stays put, however fast you click; only purely client-side things, such as moving the camera, update in between.

Microgrind's drills run on the same step: one tick every **600 ms**. Every rule in the drills (when a strike counts, when a ward blocks, when a monster swings back) is decided tick by tick by one deterministic simulation, which is what the rest of this page is built on.

## How many ticks per second?

One tick every 0.6 seconds is **1.67 ticks per second**, or exactly **5 ticks every 3 seconds**. A minute holds 100 ticks, which makes conversions easy: ticks per minute is just 100.

*How many ticks fit in a stretch of time (at exactly 600 ms per tick)*

| Time | Ticks |
| --- | --- |
| 1 second | 1.67 |
| 3 seconds | 5 |
| 1 minute | 100 |
| 10 minutes | 1,000 |
| 1 hour | 6,000 |

Going the other way is often more useful, because attack speeds and skilling cycles are counted in ticks:

*How long a number of ticks lasts*

| Ticks | Seconds |
| --- | --- |
| 1 | 0.6 |
| 2 | 1.2 |
| 3 | 1.8 |
| 4 | 2.4 |
| 5 | 3.0 |
| 6 | 3.6 |
| 7 | 4.2 |
| 8 | 4.8 |

> **Real servers drift a little**
>
> The 0.6 seconds is the target, not a guarantee. The OSRS Wiki reports that busy worlds run slightly longer ticks on average than quiet ones, and that a server can occasionally miss a tick ([source](https://oldschool.runescape.wiki/w/Game_tick)). Microgrind's tick is always exactly 600 ms, so it trains the rhythm, not any one world's quirks.

## Which tick does a click land on?

This is the part that trips people up. A click does not take effect when you make it. It waits in a queue, and the whole queue is handled at the next tick. In Microgrind the rule is exact: if tick *k* happens at `t0 + k × 600 ms`, an input made at time `ts` is applied on tick

`floor((ts − t0) / 600) + 1`

In words: the **next** tick boundary after the click, never the current one. Every click inside the same 600 ms window lands on the same tick, whether it came early in the window or a moment before the end.

*Diagram: Ticks 0 to 4. Two clicks between tick 1 and tick 2 are both applied on tick 2.*

*Any click inside the shaded window is applied together on tick 2. Where in the window it came makes no difference to the game.*

Some worked examples, computed with the same function the drills use (times are milliseconds after tick 0):

*Where a click lands, and how long it waits*

| Click at | Applied on | Tick happens at | Waits |
| --- | --- | --- | --- |
| 0 ms | tick 1 | 600 ms | 600 ms |
| 150 ms | tick 1 | 600 ms | 450 ms |
| 450 ms | tick 1 | 600 ms | 150 ms |
| 590 ms | tick 1 | 600 ms | 10 ms |
| 599 ms | tick 1 | 600 ms | 1 ms |
| 600 ms | tick 2 | 1200 ms | 600 ms |
| 601 ms | tick 2 | 1200 ms | 599 ms |
| 1250 ms | tick 3 | 1800 ms | 550 ms |

Two things stand out. A click can wait anywhere from a hair over nothing to a full 600 ms, depending only on where in the window it fell. And a click exactly on a boundary (600 ms) does not make that tick: it is queued for the one after.

In [Tick Sense](https://microgrind.io/#/play/tick-2), two strikes inside one window are still a single strike, because the drill only asks whether you struck on that tick.

## Aim for the window, not the beat

Because of that rule, clicking exactly *on* the beat is the riskiest moment. A click 1190 ms after tick 0 lands on tick 2; one at 1210 ms waits for tick 3. Twenty milliseconds of difference cost a whole tick.

*Diagram: Ticks 1 to 3. A click just before tick 2 lands on tick 2; a click just after it lands on tick 3.*

*1190 ms lands on tick 2 after 10 ms; 1210 ms misses it and waits 590 ms for tick 3.*

So the habit to build is to click comfortably inside the window *before* the tick you want, not to chase the beat itself. Try it: start the metronome and click, tap or press `Space` along with it. Each click shows the tick it lands on and how long before that tick it was made.

After every Tick Sense or Ward Flicking run, Microgrind's results screen draws the same thing for your whole run: where in the tick your inputs fell, and the median time before the tick. That sub-tick timing is feedback only. It never changes a score, because only the tick an input landed on is part of the result.

## How Tick Sense grades a strike

Tick Sense turns the rule into a drill. A target on tick *T* needs a strike applied on *T*, which means a strike made at some point during the 600 ms before it. These grades come from running the drill's own code on its first level:

*Strike timing and what the track levels award for it*

| Strike applied | Grade | Points | Target counts as |
| --- | --- | --- | --- |
| On the target tick | perfect | +100 | hit |
| One tick before it | early | −50 | missed |
| One tick after it (target missed) | late | −50 | missed |
| Nowhere near a target | stray | −50 | unchanged |

In the rhythm levels (5 and 6) an early or late strike scores nothing but costs nothing either, and the count restarts from where you actually struck, so one slip does not ruin the rest of the run. Medals ask for 95%, 80% and 60% of the maximum score.

*The Tick Sense ladder*

| Level | What it trains | Cue | Metronome | Targets | Gold |
| --- | --- | --- | --- | --- | --- |
| [1. First Beat](https://microgrind.io/#/play/tick-1) | A click is held until the next tick, so any moment in the 0.6s before it counts. | Beat track shows each target | Every beat | 16 | 1520+ points |
| [2. Back to Back](https://microgrind.io/#/play/tick-2) | One strike per tick, every tick: the base rhythm of 1-tick techniques. | Beat track shows each target | Every beat | 24 | 2280+ points |
| [3. Count It](https://microgrind.io/#/play/tick-3) | Count ticks by ear. Beat 1 is the next click you hear. | Each target called out as a beat number | Every beat | 14 | 1330+ points |
| [4. Silent Count](https://microgrind.io/#/play/tick-4) | Keep the 0.6s tempo in your head once the clicks stop. | Each target called out as a beat number | First 2 beats only | 12 | 1140+ points |
| [5. Three-Step](https://microgrind.io/#/play/tick-5) | Hold a steady 3-tick cycle, the rhythm behind tick-manipulation skilling. | Strike every 3 beats | Every beat | 20 | 1900+ points |
| [6. Inner Clock](https://microgrind.io/#/play/tick-6) | Keep a 2-tick rhythm with no clock at all. | Strike every 2 beats | First 4 beats only | 24 | 2280+ points |

## What happens inside one tick

When a tick is processed, Microgrind works through it in a fixed order: first the queued inputs, then every enemy (timers, incoming hits, movement, attacks), then the player's own movement and attacks. One visible result: your melee hit lands on an enemy one tick after your swing. This order is part of the simulation and its tests; the drills that depend on it (flinching especially) are built around it.

## How to train it

1. [Tick Sense 1: First Beat](https://microgrind.io/#/play/tick-1) shows a beat track. Strike while the line is inside a gold box and watch where the strike lands.
2. [Tick Sense 2: Back to Back](https://microgrind.io/#/play/tick-2) puts targets on back-to-back ticks: one strike per window, every window.
3. [Tick Sense 3: Count It](https://microgrind.io/#/play/tick-3) takes the track away. Targets are called out as beat numbers and you count the metronome.
4. Levels 4 to 6 fade the metronome out until you keep the tempo, or a 3-tick or 2-tick rhythm, in your head.

If 0.6 seconds feels too quick at first, each level's practice aids can slow the tick to 0.9 or 1.2 seconds. Slowed runs are for practice and do not count for the leaderboards.

## Quick answers

### How long is a tick in OSRS?

0.6 seconds (600 milliseconds) is the standard length, though busy worlds can run very slightly longer.

### How many ticks are there per second?

1.67: five ticks every three seconds, or 100 per minute.

### Does a click happen the moment I make it?

No. It waits for the next tick, which can be almost no time at all or a full 0.6 seconds, depending on when in the tick you clicked.

## Practise this

- [Tick Sense 1: First Beat](https://microgrind.io/#/play/tick-1)
- [Tick Sense 2: Back to Back](https://microgrind.io/#/play/tick-2)
- [Tick Sense 3: Count It](https://microgrind.io/#/play/tick-3)

## Sources

- [Game tick, Old School RuneScape Wiki](https://oldschool.runescape.wiki/w/Game_tick)

---

Not affiliated with or endorsed by Jagex Ltd. Old School RuneScape is a trademark of Jagex Ltd.