Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
On a Paper server, disable the main watchdog by stopping the server, opening server.properties, setting max-tick-time=-1, saving the file, and restarting. Paper documents -1 as the value that disables the watchdog entirely. The default is 60000 milliseconds, or 60 seconds.
That setting removes an important automatic shutdown safeguard. A watchdog message means the server thread stopped completing ticks, so investigate logs, crash reports, plugins or mods, world-generation and chunk-loading work, and CPU, memory, or storage pressure before making the change permanent. The exact setting also depends on the server implementation: Paper and Spigot-style servers use files and units that differ from many vanilla, Fabric, or Forge-style setups.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
Quick procedure for a Paper server
- Stop the server cleanly. Do not edit a live configuration file while the process is writing to it or while players are connected.
- Open the server root directory. This is the folder containing the server configuration and world folders.
- Edit
server.properties. Find the exact linemax-tick-time=60000, or whatever value is currently present. - Set the value to
-1. The final line must readmax-tick-time=-1. If the property is missing, add that line using the exact key spelling. - Save the file and restart the server. The new value is read during startup; it does not change a process that is already running.
Paper’s documented wording is unambiguous: “Setting this to -1 will disable watchdog entirely.” Do not add spaces to the key, change the hyphens, or put the setting in a different configuration file.
What the watchdog does
A Minecraft server advances the world in discrete ticks. The normal target is approximately 0.05 seconds per tick, equivalent to 20 ticks per second. The main watchdog checks whether the server thread has completed a tick within the configured maximum time.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
In Paper’s server.properties reference, max-tick-time is the maximum number of milliseconds that one tick may take before the watchdog stops the server. The documented default, 60000, allows 60,000 milliseconds—60 seconds—for a single tick. A tick that exceeds that limit is treated as a crash, and the process is forcibly terminated by calling System.exit(1).
A 60-second tick is far outside normal operation. Players may see severe lag or a frozen world long before the watchdog acts, because the server can stop processing movement, block updates, scheduled tasks, and other work while one tick is still waiting. The watchdog is therefore a last-resort response to a stalled server thread, not a performance setting that makes a slow server healthy.
Choose the least risky change
Disabling the watchdog is only one of several ways to respond to a timeout. Choose based on whether you need diagnosis, extra headroom for an unusually long operation, or no automatic shutdown at all.
| Approach | Configuration | What it does | Trade-off |
|---|---|---|---|
| Keep the default | max-tick-time=60000 (the documented Paper default) |
Stops the process when one tick exceeds 60 seconds. | Provides automatic protection, but a legitimate operation that stalls longer than 60 seconds can still trigger a shutdown. |
| Increase the timeout | Set a larger positive millisecond value in server.properties |
Allows one tick to run longer before the watchdog intervenes. | Delays recovery and can leave players waiting through an even longer freeze. No universally safe replacement value is established. |
| Disable the main watchdog | max-tick-time=-1 |
Removes the automatic shutdown threshold for the main watchdog. | A hung process may remain indefinitely and may not recover without manual intervention. |
| Retain warnings only | Use Paper warning controls, without changing the shutdown threshold | Keeps diagnostic warning behavior while preserving automatic shutdown. | Warnings do not prevent a later watchdog termination if the server remains unresponsive. |
For a short diagnostic session, increasing the timeout can preserve a safety net while you collect evidence. For a permanent production configuration, first establish why ticks are stalling; otherwise, a full disable can conceal a recurring fault.
Why you should diagnose the stall first
The watchdog does not identify one universal root cause. It reports that the server thread has failed to make progress within the configured interval. Different incidents can look identical from the watchdog’s perspective.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
- Read the watchdog section of the console output and any generated crash report. Note the thread stack and the operation shown at the time of the stall.
- Review the server log immediately before the timeout for plugin or mod errors, repeated exceptions, world-save messages, or long-running tasks.
- Temporarily remove or update a recently added plugin or mod, using a backup and a controlled restart so that you can identify whether behavior changes.
- Check whether world generation, chunk loading, a large teleport, or another bulk operation coincided with the freeze.
- Check CPU saturation, available memory, garbage-collection pressure, and storage latency on the host. A resource graph covering the incident is more useful than a single reading taken after recovery.
- Confirm that the server process is using the intended Java runtime and that the host has not imposed a CPU, memory, or I/O limit.
These checks are operational guidance based on the watchdog’s role. Paper’s documentation defines the timeout and warning behavior but does not claim that one of these causes explains every shutdown.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Editing server.properties safely
Stop before editing
Use the normal stop control supplied by your host, panel, service manager, or console. Wait for the process to finish saving and for the console to indicate that it has stopped. A forced kill can interrupt a world save and makes it harder to distinguish a watchdog incident from a damaged or incomplete shutdown.
Find the correct file
The file belongs in the server root, alongside the server’s other configuration files. If you operate several instances, verify the directory by checking the running service’s working directory or the panel’s selected instance. Editing a similarly named backup or a different world directory will have no effect.
Change only the relevant property
Open the file as plain text. Locate the key by its exact spelling, max-tick-time. Replace only its value, leaving the equals sign and key intact:
max-tick-time=-1If there is no such line, add it on its own line. Do not put it under a YAML indentation level, add quotation marks, or write a unit suffix such as s or ms; the value is an integer interpreted as milliseconds by the Paper server property.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Save, then restart
Save the file without changing its encoding or filename. Start the same server instance you stopped. If a control panel generates configuration from a template, check that it did not overwrite your edit during startup; the effective value is the one shown in the instance’s actual server.properties file.
Understanding the time units
Paper’s server.properties value is measured in milliseconds. Thus, 60000 means 60 seconds, while 120000 would represent two minutes if you deliberately chose that positive value. The normal tick target of about 0.05 seconds is not the watchdog threshold; it is the rate the server tries to maintain under ordinary load.
Spigot-style configuration introduces a separate unit convention. Paper’s spigot.yml reference describes settings.timeout-time in seconds as the time since the last server tick before the server is considered unresponsive and stopped or restarted. Paper’s documentation explains that this mirrors the vanilla-like server.properties concept but uses seconds instead of milliseconds. Always identify the file and unit before converting a value.
Paper and Spigot settings that are easy to confuse
spigot.yml settings.timeout-time
This setting is a Spigot-style timeout expressed in seconds. It is not the same text key or unit as server.properties max-tick-time. If you are following a guide written for one file while editing the other, you can unintentionally choose a value that is 1,000 times different from what you intended.
Free tools Windows power users keep installed
One-click scans. No signup required.
spigot.yml tile and entity limits
Some configurations show max-tick-time.tile and max-tick-time.entity. Paper documents these options as disabled or non-functional. Changing them is not a reliable way to stop the main watchdog, and they should not be presented as substitutes for server.properties max-tick-time=-1.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
The disable.watchdog Java property
Paper also documents a separate Java system property named disable.watchdog. Its purpose is to disable the watchdog warning system. That is different from disabling the main shutdown threshold. A warning-only change can alter diagnostic output while the server remains subject to automatic termination when the configured tick limit is exceeded.
Do not assume that setting disable.watchdog alone keeps a frozen server alive. If your goal is to stop automatic process shutdown, the documented Paper setting is still max-tick-time=-1 in server.properties.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The paper-global.yml watchdog section
Paper’s paper-global.yml contains a watchdog section for early-warning behavior. These controls help determine how Paper reports impending or detected stalls; they do not replace the main max-tick-time shutdown setting. Keep the distinction clear when testing a warning adjustment versus removing the shutdown safeguard.
Server implementation matters
The procedure above is specifically for Paper’s documented server properties and applies to Paper-based deployments that use that file. Spigot-style servers additionally expose settings in spigot.yml, including the seconds-based timeout described above.
Vanilla, Fabric, and Forge-style servers may use a vanilla-like server.properties, but the available keys, watchdog implementation, and version behavior must be confirmed for that server software and release. Do not copy a Paper-only key into a configuration format that does not recognize it and assume the watchdog is disabled. If the server’s own reference does not document max-tick-time=-1, treat the Paper procedure as unverified for that implementation.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Likewise, a hosting panel can expose a text editor, environment variable, or startup template instead of the filesystem directly. The authoritative test is whether the running instance reads the intended property from its own configuration at startup.
How to verify the change
- After restarting, stop the server again and reopen the same
server.propertiesfile to confirm thatmax-tick-time=-1remains present. - Check the startup log for configuration errors. A malformed key, an accidental quotation mark, or an edit to the wrong instance can leave the old value in effect.
- Confirm that the process you started is the same Paper instance whose root directory you edited. Multi-instance hosts commonly have several similarly named folders.
- Do not deliberately freeze a production world merely to test the watchdog. If you need to validate configuration, use a backup or disposable test instance and observe normal startup behavior and logging.
Successful verification means the setting is present in the active instance; it does not mean the underlying stall has been fixed. Continue monitoring tick health and resource usage after the restart.
Recovering from a server that is already stuck
If the console shows that the server has not responded for 10 seconds, as in Paper’s troubleshooting example, first allow the watchdog to complete its normal diagnostic and shutdown behavior when possible. Capture the console output and crash report before deleting or rotating logs.
If the process remains unresponsive and you have deliberately disabled the watchdog, use the host’s normal stop action. Escalate to a forced termination only when a clean stop cannot complete, and make a backup of the world before restarting. A forced termination can leave pending writes incomplete, so treat the next startup as a recovery event rather than proof that the configuration solved anything.
When increasing the timeout is better than disabling it
A positive, larger timeout can be a temporary compromise when you understand that a specific operation may exceed 60 seconds but still expect the server to return to normal. It preserves an upper bound and allows the watchdog to stop a process that never resumes. Because no universally safe replacement value is established, choose any increase only from measurements of the actual operation and leave room for the host’s resource limits.
Document the temporary change, schedule a return to the normal value, and watch whether players experience a frozen server during the longer interval. If the operation repeatedly approaches the new limit, the configuration is masking a capacity or software problem rather than solving it.
When a permanent disable may be justified
A permanent -1 setting can be appropriate for a controlled diagnostic environment, a development test in which an operator is present, or a deployment with an external supervisor that has its own carefully tested recovery policy. It is a poor default for an unattended public server when no one can detect and restart a hung process.
- Keep recent backups before testing long-running operations.
- Ensure an operator can reach the console or service manager.
- Retain logs and crash reports even if warning output is adjusted.
- Monitor process liveness, tick responsiveness, CPU, memory, and storage separately; a process that still exists may not be serving players.
- Set a review date for the change and restore the normal watchdog after the underlying issue is resolved.
Restoring the watchdog
To re-enable the documented Paper safeguard, stop the server cleanly, edit server.properties, and replace max-tick-time=-1 with the desired positive millisecond value. Restoring the documented default means using max-tick-time=60000. Save the file and restart the instance. If you changed warning controls separately, review those files as well so that diagnostic messages match your operational policy.
Quick Recap
Key takeaways for administrators
- For Paper, the direct disable value is
max-tick-time=-1inserver.properties. - The documented default is
60000milliseconds, or 60 seconds, for one tick. - Paper’s main watchdog can terminate the process with
System.exit(1)after a timeout. spigot.ymlsettings.timeout-timeuses seconds and is a separate setting.- Paper’s tile and entity
max-tick-timeentries are documented as disabled or non-functional. disable.watchdogand thepaper-global.ymlwatchdog section concern warning behavior; they do not replace the main shutdown threshold.- A watchdog event signals a severe stall. Diagnose the cause before removing the protection, and use a reversible, monitored change whenever possible.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
