What Are Game Ticks and Redstone Ticks?
Like gears in a clock synchronized to a pendulum, every task in Minecraft's simulation is synchronized to one central game loop. One cycle of this loop is called a game tick. Under normal conditions, the game runs at a fixed rate of 20 game ticks per second (TPS), meaning one game tick occurs every 0.05 seconds (50 milliseconds).
A redstone tick is a unit of time equal to exactly two game ticks, or 0.1 seconds. Redstone ticks are not a separate engine loop handled by distinct game logic; rather, the term was coined by the community to make discussing circuits easier because most redstone components take a multiple of 2 game ticks to change states. When discussing redstone circuits, the word "tick" should always be interpreted as a redstone tick unless specified otherwise.
Exact Timing Rules and Numbers
Understanding how the game processes time helps you calculate exact delays and diagnose lag:
- Game Loop & Day Cycle: At 20 TPS, a full in-game day lasts exactly 24,000 game ticks (20 real-world minutes), and the world autosaves every 6,000 game ticks.
- Repeater Delays: A redstone repeater can be set to a delay of 1 to 4 redstone ticks, which corresponds to 2, 4, 6, or 8 game ticks.
- Scheduled Ticks & Priority: Blocks that change state in a predictable pattern request a "scheduled tick" for a future game tick. During the scheduled block tick phase, blocks execute based on priority (lowest number goes first) and then by scheduling order. A repeater facing the back or side of another diode has priority
-3; a depowering repeater has priority-2; other repeaters and comparators facing the back or side of another diode have priority-1; all other block ticks have priority0. Fluid ticks run after block ticks and do not use priorities. - TPS and MSPT: Milliseconds per tick (MSPT) measures how much real time a server takes to compute one game tick. To maintain a full 20 TPS, MSPT must stay at 50 or below. If the computer cannot keep up, TPS drops, and because game actions are timed by tick count rather than wall-clock time, contraptions take longer to run.
- Random Ticks: During every chunk tick, blocks are randomly selected in each 16×16×16 subchunk section to receive a random tick (which grows crops, decays leaves, or turns off lit redstone ore). The median interval between random ticks on a given block is 47.30 seconds (946.03 game ticks), and the average is 68.27 seconds (1365.33 game ticks).
Step-by-Step Build: Visualizing 1 Second in Redstone Ticks
Because 1 redstone tick equals 0.1 seconds (2 game ticks), exactly 10 redstone ticks equal 1 full second (20 game ticks). You can build a simple 1-second delay line to see this conversion in action:
- Place a solid opaque block on the ground and attach a lever to it.
- Place a line of 3 redstone repeaters leading away from the block, all facing the same direction.
- Right-click the first repeater three times to set it to its maximum delay of 4 redstone ticks (8 game ticks).
- Right-click the second repeater three times to set it to 4 redstone ticks (8 game ticks).
- Right-click the third repeater once to set it to 2 redstone ticks (4 game ticks).
- Place a redstone lamp at the output of the third repeater.
- Flip the lever on. The signal will travel through
4 + 4 + 2 = 10redstone ticks (20 game ticks) of delay, turning the lamp on exactly 1.0 second after you flicked the switch (assuming your world is running at a steady 20 TPS).
How Players Use Tick Timing and Reduce Lag
Players rely on redstone tick math to synchronize pistons, shape pulses, and manage server performance:
- Synchronizing Parallel Lines: When a signal splits into two paths, players count the redstone ticks of torches, repeaters, and comparators along each branch to ensure both signals arrive at the destination on the exact same game tick.
- Diode Priority Control: Technical builders exploit the scheduled tick priorities (
-3,-2,-1) of repeaters and comparators to control the exact order in which components update within the very same game tick. - Monitoring Server Health: In singleplayer or as a multiplayer host, players check the F3 debug screen (where MSPT is shown as "ms ticks") and the frame time graph to verify that MSPT is under 50.
- Lag Mitigation: Redstone dust and active machinery generate excessive block updates that raise MSPT. Builders add master off-switches to disable redstone clocks when not in use, and they place blocks with inventory slots or composters on top of exposed hoppers to stop them from constantly searching for items above them.
Common Mistakes
- Confusing Game Ticks with Redstone Ticks: Setting a repeater to "1 tick" delays the circuit by 1 redstone tick (0.1s), which is 2 game ticks. If a technical tutorial asks for a 4-game-tick delay, you only need a repeater set to 2 redstone ticks, not 4.
- Sending 1-Tick Pulses into Torches or Comparators: Very short pulses (1 or 2 ticks) can fail to trigger certain components because of their internal update sequences. For example, a redstone torch or a redstone comparator will not respond to a 1-tick pulse.
- Expecting Constant Real-Time Speed on Laggy Servers: Circuits count ticks, not seconds. If heavy mob AI, uncovered hoppers, or flashing redstone dust push MSPT above 50, TPS drops below 20 and your 10-redstone-tick delay will take longer than 1 real-world second.
