Minecraft operates on a single-threaded game loop that updates the world, handles entities, and processes block changes in sequence. A built-in monitor tracks the duration of these cycles and terminates the server if a single update exceeds the configured limit, preventing deadlocks. Administrators can change the max tick time setting to accommodate hardware constraints, complex world generation, or extensive modifications that cause processing spikes.
Step 1. Log in to the MelonCube Games panel.
Step 2. Stop the server.
Step 3. Go to the Config Files on the left and select Server Config.
Step 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. |
Step 5. Start the server.