What Is the Default Tick Speed in Minecraft — And What Does It Actually Control?
Minecraft runs on an internal clock that governs almost everything happening in your world — crop growth, weather changes, fire spread, mob behavior, and redstone timing. That clock is measured in game ticks, and understanding the default tick speed helps explain why your farm grows at a certain pace or why your redstone contraption behaves the way it does.
What Is a Game Tick in Minecraft?
A game tick is the smallest unit of time in Minecraft's engine. The game processes one tick roughly every 50 milliseconds, which works out to 20 ticks per second at full speed. Think of it like frames in an animation — every tick, the game recalculates mob positions, processes block updates, checks conditions for plant growth, and runs every other active system in the world.
This 20-tick-per-second rhythm is fixed to real time, not to your frame rate. Even if your graphics are rendering at 60 FPS, the game logic still advances at 20 ticks per second under normal conditions.
What Is the Default Random Tick Speed?
Within that 20-tick-per-second framework, there's a separate and more specific setting: randomTickSpeed. This controls how often random block updates are applied throughout the world.
The default randomTickSpeed value is 3. This is the setting for both Java Edition and Bedrock Edition, though how each edition calculates and applies random ticks internally differs slightly at the technical level.
Each game tick, Minecraft selects a number of random blocks in each loaded chunk section (a 16×16×16 area) and applies an update to them. That number of selections per chunk section per tick is what randomTickSpeed controls. At the default of 3, three random block selections happen per chunk section per tick.
What Does randomTickSpeed Actually Affect?
Random ticks govern a wide range of in-game processes: 🌱
- Crop growth — wheat, carrots, potatoes, beetroot, and similar plants grow based on random ticks
- Grass spreading — grass blocks spread to adjacent dirt via random ticks
- Leaf decay — leaves detach from trees after the log is removed through this system
- Fire spread and burnout — fire blocks use random ticks to spread or extinguish
- Composting and some plant mechanics — including sugar cane, bamboo, and kelp growth rates
- Snow and ice melting — in warmer biomes, this is tick-driven
- Farmland drying out — unirrigated farmland reverting to dirt uses random ticks
Processes that are not governed by randomTickSpeed include redstone timing, mob AI cycles, and hopper transfer rates — those run on the fixed 20-tick-per-second game clock regardless of your randomTickSpeed setting.
How to Check or Change the Tick Speed
You can view or change the randomTickSpeed using the /gamerule command in-game:
- Check current value:
/gamerule randomTickSpeed - Set to default:
/gamerule randomTickSpeed 3 - Increase speed:
/gamerule randomTickSpeed 10(faster growth, faster fire spread) - Disable random ticks:
/gamerule randomTickSpeed 0(plants stop growing entirely)
This command requires cheats enabled in Java Edition or operator permissions on a server. In Bedrock Edition, the same command works with appropriate permissions.
How Tick Speed Shapes the Game Experience ⏱️
The default of 3 is calibrated to create a gameplay pace where farming and survival feel balanced — crops grow slowly enough to require planning, but fast enough to feel rewarding. Changing this value creates noticeably different experiences:
| randomTickSpeed Value | Effect |
|---|---|
| 0 | Plants and fire frozen — no random block updates |
| 1–2 | Slower than default; crops take longer to mature |
| 3 | Default — balanced vanilla pace |
| 10–20 | Noticeably faster crop growth and fire spread |
| 100+ | Extreme speed — instant-feeling growth, rapid fire propagation, potential performance impact |
Very high values don't just accelerate farming — they also accelerate every tick-driven process simultaneously. Fire becomes extremely aggressive, leaf decay happens almost instantly, and on lower-end hardware, processing thousands of additional random block updates per second can cause lag or world instability.
Server Performance and Tick Rate
On multiplayer servers, the overall tick rate matters as much as randomTickSpeed. A healthy server maintains 20 TPS (ticks per second). When a server drops below 20 TPS — due to too many loaded chunks, complex redstone machines, or a high player count — the game world slows down relative to real time. Crops grow more slowly in real-world minutes, mobs react sluggishly, and timers stretch out unpredictably.
This is an important distinction for server administrators: TPS lag and randomTickSpeed are separate variables. A farm that feels slow might not need a randomTickSpeed adjustment — it might need server optimization instead.
The Variables That Determine What's Right for Your World
The default tick speed of 3 works well for standard survival gameplay, but whether that's appropriate for your specific world depends on factors only you can assess:
- World type — creative builds, survival servers, and farming-focused worlds all have different needs
- Hardware — increasing randomTickSpeed significantly raises CPU load per tick cycle
- Game mode goals — speedrunning, peaceful farming, and technical redstone builds prioritize different tick behaviors
- Edition — Java and Bedrock handle some tick calculations differently, which can produce slightly different results even at the same setting
- Server population — shared worlds need to balance one player's tick preference against everyone else's performance
Understanding what the default value is and what it controls puts you in a much better position to evaluate whether the vanilla setting fits how you're actually playing — or whether your specific setup calls for something different.