What a tick is
A tick is one step of the game simulation, nominally lasting 50 milliseconds. Twenty of them make a second, which is the pace Minecraft was designed around: mobs move, crops grow, and redstone fires on that schedule.
When a tick takes longer than 50 ms, the server runs fewer of them per second, and the whole world slows rather than skipping content.
TPS versus MSPT
TPS counts how many ticks completed; MSPT measures how long each one took. They describe the same reality from opposite directions, and MSPT is the more useful number because it shows headroom before problems start.
A server can report a comfortable-looking TPS average while MSPT spikes badly, because the average smooths over the moments players actually notice.
Reading a TPS number
20 means the server is keeping up. Around 18–19 something is slightly overloaded and observant players may feel it. Below about 15, block breaking and mob movement are visibly sluggish, and below 10 the server is effectively unusable.
Because vanilla has no /tps command, servers read it from the panel graph, from spark, or from the debug report.
Why averages mislead
TPS is usually reported over a window, which hides spikes. A server that runs at 20 for four minutes and drops to 5 during a player’s exploration still averages well, while the experience is terrible.
Always pair the number with a cause: if TPS dips when players explore, chunk generation is the story; if it dips when a farm runs, entities are.
FAQ
Common questions
Is TPS the same as FPS?
No. FPS is how smoothly your client renders the world and depends on your graphics hardware. TPS is how fast the server simulates it, and it affects every player equally, no matter how powerful their computer is.
Can TPS go above 20?
No. The server deliberately sleeps to hold the 20-tick-per-second pace. A TPS reading above 20 is a measurement artifact, not a faster server.
