How to Change Tick Speed in Minecraft

Tick speed is the metronome of Minecraft. Every block update, every mob decision, every crop pushing one stage higher: it all runs on the game’s tick clock. The default is 20 ticks per second (TPS), but two separate values actually shape what happens in your world: the game tick rate (how fast the whole simulation runs) and the Minecraft random tick speed (how often individual blocks get a chance to update). Both can be changed, and changing them opens up everything from rapid farms to slow-motion redstone debugging.

What Is Tick Speed in Minecraft?

In Minecraft, ‘tick speed’ is shorthand for two related but different values. Both control how fast the game world simulates, but they affect different parts of it. Once you know which one to touch, the actual commands take seconds.

Minecraft Normal Tick Speed

The Minecraft normal tick speed is the game’s overall update rate, locked to 20 TPS by default. Every tick, Minecraft processes the entire game loop: player movement, mob AI, redstone signals, the day-night cycle, projectile physics, the lot. If your server can’t keep up, TPS drops and everything in the world slows down with it. Until Minecraft 1.20.5 this rate was completely fixed, but Mojang has since added the /tick command, which lets operators:

• speed it up
• slow it down
• freeze it entirely
• sprint through thousands of ticks in seconds

Minecraft Random Tick Speed

Minecraft random tick speed is a game rule that controls how often individual blocks get a chance to update independently of the main loop. Every game tick, Minecraft picks a handful of blocks at random in each loaded chunk section and gives them a ‘random tick’. That’s how crops grow, fire spreads, ice melts, leaves decay and saplings sprout. The default value is 3 on Java Edition and 1 on Bedrock Edition. Raise it and these processes accelerate; lower it and they crawl; set it to 0 and they stop happening at all.

The Minecraft Tick Speed Command: Two Ways to Change It

There are two separate Minecraft tick speed commands, and they do not overlap. Use:

1. /gamerule randomTickSpeed to change how fast blocks update
2. /tick rate to change how fast the entire game runs

Both require cheats to be enabled, or operator status on a multiplayer server.

Change Random Tick Speed With /gamerule

This is the classic Minecraft tick speed adjustment most guides cover. Three steps:

1. Press T to open the chat window.
2. Type /gamerule randomTickSpeed <value> – for example /gamerule randomTickSpeed 10.
3. Press Enter. The change applies instantly and persists across saves.

Common values: 0 disables random ticks entirely, 3 is the Java default, 1 is the Bedrock default, and anything from 10 to 40 is the typical sweet spot for fast farming without melting the chunk simulation. On Bedrock Edition you can also change this through the world settings menu without typing a command. Just open the pause menu, scroll to “Cheats” and look for the Random Tick Speed slider.

Change Normal Tick Rate With /tick

Added in Minecraft 1.20.5 (Java Edition only), the /tick command is the answer to ‘can you change the actual tick rate?’ It’s also a major reason older guides are now outdated. It needs operator level 3, so it works on any world with cheats and on any server where you have full admin rights.

Subcommand	What it does
/tick rate <value>	sets target TPS, range: 1.0 to 10000.0, default: 20
/tick query	shows current TPS & mean tick time
/tick freeze	pauses simulation, players (and any entity they’re riding) keep moving
/tick unfreeze	resumes normal ticking
/tick step <ticks>	while frozen, advances the world by the given number of ticks; useful for redstone testing
/tick sprint <ticks>	runs game as fast as the hardware allows for the given number of ticks, then resumes previous rate

Setting /tick rate 40 doubles the world’s speed: crops grow twice as fast, mobs move twice as fast, day-night cycles fly by. Setting /tick rate 5 turns the world into slow motion. Note that the /tick command does not exist on Bedrock Edition. There, only the random tick speed game rule is available, plus the in-game settings slider.

Why Change the Minecraft Tick Speed?

Changing tick speed isn’t just a curiosity command, but a serious tool. The most common reasons players reach for it:

• faster resource gathering: higher random tick speed speeds up crop growth, sapling growth, kelp and bamboo farms, and sugar cane production
• redstone testing: /tick freeze + /tick step 1 lets you advance the world one tick at a time, which is invaluable when debugging redstone circuits with tight timing
• time-skipping: /tick sprint 24000 fast-forwards a full Minecraft day in seconds, great for testing long-running farms or waiting out a thunderstorm without sleeping
• performance tuning: lowering /tick rate on a struggling server is a desperate-but-effective way to keep gameplay coherent when the hardware can’t sustain 20 TPS
• custom gameplay: slow-motion challenge runs, speedrun-style accelerated worlds, or quirky game mode variants

Risks & Limits of Changing the Minecraft Tick Speed

Both commands can wreck a world if you push them too far. The most common failure modes:

• fire spreads uncontrollably
• servers freeze under load
• day-night cycles desync chunks
• Bedrock Edition behaves differently

Random tick speed at 50 means fire jumps blocks faster than you can place stone. A single torch in a wooden base can flatten everything before you react. A high /tick rate on a server with limited resources will also pin the CPU and tank TPS to single digits. If you’re running into this, the answer is usually more RAM, not more ticks. Very high tick rates can cause visible chunk loading lag and mob-spawning weirdness, especially in modded worlds. The Minecraft random tick speed on Bedrock isn’t a 1-to-1 block count, but a relative multiplier, so the same number means something else than on Java.

The fix is always the same: reset to defaults. /gamerule randomTickSpeed 3 (Java) or 1 (Bedrock), and /tick rate 20 for the main loop.

Tick Speed on Your Minecraft Server

On a hosted Minecraft server, both commands behave the same way as in singleplayer, but with two practical differences. First, you need operator status to run them. Second, neither value persists in server.properties the way difficulty or game mode does, so a server restart resets /tick rate to 20 (but keeps randomTickSpeed because it’s stored in the world’s level data, not the config). If you want a permanent random tick speed override, run the /gamerule command once and it’ll stick across restarts.

For server admins, the most useful pattern is combining /tick with the standard admin commands. Freeze the world to do maintenance without despawning mobs. Sprint through 30 minutes of darkness while you brief your players. Slow the rate to investigate a runaway redstone trap without it firing again. And when an automated farm design is too slow to test in real time, sprint a few thousand ticks and see what it actually produces.

FAQ

Tick, Tock – Time to Take Control of Your World

Minecraft tick speed is one of the most powerful sliders in the game, and now that the /tick command exists, you have control over both halves of it: the per-block randomness and the global game clock. Whether you’re chasing faster harvests, debugging a redstone contraption frame by frame, or just want to skip an in-game night without sleeping, a single command gets you there. Just remember to put it back to 20 and 3 when you’re done. Otherwise, future-you will wonder why every torch is suddenly a flamethrower. Want to play with tick speed without worrying about your laptop melting? Rent your Minecraft server from GPORTAL, hand yourself operator rights, and run /tick and /gamerule with full admin control – your friends keep playing while you bend time.

similar articles