Tick Command Generator — /tick query, rate, freeze, step, sprint
Run these from an operator’s chat, a command block, or a function file. Stopwatch and Fetchprofile are newer commands — check availability on your Minecraft version.
How to Use the Tick Command Generator
- Pick a mode: Query reports current status, Rate changes the target ticks-per-second, Freeze/Unfreeze pauses or resumes simulation, Step advances a frozen world by a set amount, or Sprint runs ticks as fast as the hardware allows for a set time.
- For Rate, type the new target ticks-per-second (20 is vanilla default).
- For Step, optionally type a duration like
1t– leave blank to step exactly one tick. - For Sprint, choose Time (with a duration like
60s) or Stop to cancel an in-progress sprint. - Copy the generated
/tickcommand into the console or an operator’s chat.
Command Syntax Reference
/tick query /tick rate <rate> /tick freeze /tick unfreeze /tick step [time] /tick sprint <time> /tick sprint stop
/tick query reports the current target tick rate, the actual milliseconds-per-tick (MSPT) the server is achieving, and whether the simulation is currently frozen. /tick rate 10 changes the target rate from the vanilla 20 ticks per second down (or up) to a custom value – useful for intentionally slowing a world down for cinematic or debugging purposes. /tick freeze stops entity movement and block ticking entirely (players can still walk around and open menus, but nothing else updates); /tick unfreeze resumes normal simulation. While frozen, /tick step 1t advances the world by exactly one tick (or by whatever duration you specify) so you can inspect frame-by-frame behavior. /tick sprint 60s does the opposite of freezing – it runs as many ticks as the server can process for 60 seconds, useful for fast-forwarding crop growth or redstone contraptions; /tick sprint stop cancels a sprint early.
Frequently Asked Questions
What’s the difference between /tick freeze and just lagging?
Lag is unintentional – the server falls behind and ticks arrive late. /tick freeze is a deliberate, clean pause: block updates and entity AI stop completely and predictably, rather than just running slowly, which makes it useful for taking a screenshot or inspecting a moment in time without motion blur from things still moving.
Can players still move around while the world is frozen?
Yes – freezing stops world simulation (entities, block ticks, redstone) but players retain normal client-side movement and can still open inventories and menus; it’s the simulation that pauses, not player input.
What does /tick step actually let me do that freeze alone doesn’t?
Freeze alone just holds the world still indefinitely. /tick step advances it by a controlled, small amount (default one tick) while remaining otherwise frozen, which is exactly what you want for stepping through redstone timing or an entity’s exact tick-by-tick behavior.
Is /tick sprint the same as raising the tick rate with /tick rate?
No – raising the rate with /tick rate changes the target pace the server aims for continuously going forward, while /tick sprint is a temporary burst that processes ticks as fast as hardware allows for a fixed duration, then returns to the previous rate automatically.
Related Tools
- Debug Command Generator – profile exactly what’s consuming tick time.
- Test Command Generator – run GameTest structures that benefit from stepping ticks manually.
- Stopwatch Command Generator – measure elapsed time across frozen or sprinted ticks.