Aller au contenu

A TPS query used the wrong execution context

Paper may log the console command tps as called asynchronously. A monitoring query is one possible source. This line alone establishes neither a crashed server nor a low tick rate.

An example of this log message

Unexpected exception while parsing console command "tps" java.lang.IllegalStateException: Asynchronous Command Dispatched Async: tps

Identify the recurring caller

Compare timestamps with configured performance queries or plugin tasks. If your group plays normally and only this query stands out, leave world files alone. A real performance issue needs its own measurements and relevant log evidence.

For your own automation, check the call path

If you operate the query yourself, check whether it uses the command path intended for your Paper version. For managed monitoring, keep the log excerpt for support. Do not install extra performance plugins on a guess because of this warning.

Questions about this error

Do I need more RAM because tps appears?

The command name is not a resource measurement. The warning describes the call context rather than memory demand.

Can a new world fix this?

A different world does not change how the command is called.

Check a connected log excerpt