Direct answer

tps-catchup affects timekeeping after lag spikes. Disabling it can avoid rapid catch-up behavior, but does not eliminate whatever caused the stall.

How to check it

  1. Find tps-catchup in the generated global Purpur configuration.
  2. Record the server TPS and a spark profile around the lag spike.
  3. Observe whether rapid post-spike mob movement or damage corresponds to catch-up behavior.

What to change

  1. Keep an unchanged copy of purpur.yml before testing.
  2. If catch-up behavior harms gameplay, test disabling this documented option during a maintenance period.
  3. Compare identical spike workloads; address the underlying tick-time cost separately.

Software and version notes

Compatibility and safety

Purpur documents that catch-up may run faster than 20 TPS following an under-20-TPS period, potentially causing gameplay side effects. This differs from permanently increasing the target tick rate.

Verify the result

Observe player and mob behavior directly after a controlled lag spike and confirm the underlying MSPT problem is independently investigated.

References