The default tick speed in Minecraft is actually two different numbers depending on what you mean by “tick speed.” The game’s core game tick is always fixed at 20 game ticks per second, but the default random tick speed, the setting that affects crop growth, fire spread, and leaf decay, is 3 in Java Edition and 1 in Bedrock Edition. That distinction matters because most players asking about tick speed are really trying to change how fast their crops grow or how quickly fire spreads, which is governed by the random tick speed, not the fixed game tick.
Game tick vs. random tick: understanding the difference
Game ticks are the heartbeat of Minecraft, running at a constant 20 ticks per second. This fixed rate controls core mechanics like mob AI, redstone signals, and block updates. Random ticks, on the other hand, are a separate system that runs on a subset of blocks each tick, randomly selecting blocks in loaded chunks to apply effects like crop growth, grass spreading, and fire propagation. The game tick is non-negotiable, you can’t change it without mods, but the random tick speed is a gamerule you can adjust. Knowing the difference helps you avoid confusion when you see commands like /gamerule randomTickSpeed; that command only affects the random tick system, not the overall game speed.
How to check your current random tick speed
To see what your random tick speed is currently set to, you can query the gamerule directly without changing anything. Open your chat window (press T on Java Edition or the chat button on Bedrock) and type /gamerule randomTickSpeed with no value. The game will respond with the current number, letting you verify whether it’s the default 3 (Java) or 1 (Bedrock) or if it’s been changed. This is a quick, zero-risk way to confirm your setting before you decide to modify it.
How to change the random tick speed in Java Edition
Changing the random tick speed in Java Edition requires the use of a command, and you’ll need cheats enabled or operator status on a server. Here’s the step-by-step process:
- Ensure cheats are enabled in your single-player world (you can toggle this when creating the world or by opening the LAN settings and allowing cheats). On a server, you must have operator permissions.
- Open the chat window by pressing
T. - Type
/gamerule randomTickSpeed <value>, replacing<value>with the number you want. For example,/gamerule randomTickSpeed 6doubles the default Java speed. - Press Enter to apply the change. The new setting takes effect immediately.
Higher values speed up random events like crop growth and fire spread, while setting it to 0 disables them entirely. Note that this only works if you have the necessary permissions, without cheats or operator status, the command will be rejected.
How to change the random tick speed in Bedrock Edition
Bedrock Edition offers two ways to adjust the random tick speed, giving you more flexibility depending on your preference. The first method uses the same command as Java: open chat, type /gamerule randomTickSpeed <value>, and press Enter. The second method is through the world settings menu, navigate to your world’s settings, scroll to the “Cheats” section, and you’ll find a slider labeled “Random Tick Speed.” Move the slider to your desired value and save. Both methods require cheats to be enabled for the world, but the slider is more intuitive if you prefer a visual interface. Remember that Bedrock’s default is 1, so if you’ve never changed it, that’s what you’ll see.
What happens if you set the tick speed too high?
While cranking up the random tick speed might sound fun for faster farming, setting it too high can quickly ruin your game. Severe server lag is the most immediate consequence, because the game has to process far more random block updates per second, which can drop your frame rate or make the server unresponsive. Fire becomes uncontrollable, entire forests can ignite and spread faster than you can react, potentially destroying builds and terrain. Additionally, the strain on chunk simulation increases, meaning your computer or server hardware has to work much harder to keep up, which can lead to crashes or world corruption in extreme cases. The safe default values, 3 for Java and 1 for Bedrock, exist for a reason: they balance gameplay speed with performance. If you do experiment, increase the value gradually and monitor your game’s performance, and always keep a backup of your world before making drastic changes.
