The max tick time setting on a Minecraft server determines the maximum number of milliseconds a single server tick can take before the built-in watchdog forces a shutdown. Resource-intensive tasks such as generating complex terrain, loading large modpacks, or starting a world can cause temporary processing delays that exceed the default limit. Increasing this threshold provides the server additional time to complete heavy workloads and avoid a forced shutdown. Disabling the watchdog allows administrators to troubleshoot the root cause of performance issues without the system terminating the process.
1. Log in to the BisectHosting Starbase panel.
2. Stop the server.
3. Select the Config Files tab and choose Server Config.
4. In the Max Tick Time field, enter a tick rate.
| Tick Rate | Time | Description |
|---|---|---|
60000 |
60 seconds | Default. Safely shuts down the server if a freeze lasts longer than a minute. |
120000 |
120 seconds | Ideal for standard modpacks. Prevents server crashes during occasional lag spikes caused by chunk generation or entity processing. |
240000 |
240 seconds | Maximum recommended limit. The highest safe value for heavy modpacks. Exceeding this limit is not recommended, as it leads to extreme server unresponsiveness and can worsen crashes. |
-1 |
Disabled | Turns the Watchdog off completely. Necessary for massive modpacks or for developer debugging. The server may freeze indefinitely in an infinite loop rather than safely crash, requiring a manual force-kill. |
5. Start the server.