Start the tick profiler
/debug startBegins measuring server ticks until you stop it.

/debug starts and stops a tick profiler that measures how fast the server runs, and traces every command run by a function. It is a tool for data pack authors and server admins chasing lag or a function that misbehaves.
/debug function <name>/debug start/debug stop// In single player with cheats on, you have level 4, so it works there too.
| Argument | Expects | What it does |
|---|---|---|
| name | Function | ID of the function to trace, such as blockaria:tick, or a function tag starting with #. |
/debug startBegins measuring server ticks until you stop it.
/debug stopShows the recorded time, ticks and average ticks per second.
/debug function blockaria:tickRuns the function and saves every executed command to a file.
Fill in the fields, then copy the command.
Command generatordebug start begins measuring. debug stop ends it and reports the seconds and ticks recorded, with the average ticks per second. A world without lag runs at 20 ticks per second.
debug function blockaria:tick runs the /function and writes each executed command to an output file, named in chat. It cannot be called from inside a function, nor with return run. For deeper analysis, see /perf and /jfr; to slow the game down while testing, use /tick.
✓ Checked in Java Edition 26.3 · updated 2 November 2026
/debug function was called from a function. Run it from the chat, the server console or a command block instead.
/debug start runs until you stop it and reports ticks per second. /perf records a 10 second performance report and saves it as a file.
In single player with cheats on, or on a server as an operator or from the server console: /debug function <name>.
Server operator, level 3. In single player with cheats on, you have level 4, so it works there too.