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 vanilla Minecraft Java server, automatic saving runs every 6,000 game ticks—about five minutes. You cannot pause it safely by deleting a configuration key: use the runtime commands save-off, save-on, and save-all. For backups, the reliable sequence is save-off, save-all flush, copy the world files, then save-on.
Paper servers add a separate performance control. The max-auto-save-chunks-per-tick setting, located in config/paper-world-defaults.yml, limits how many chunks are written during each tick; its documented default is 24. That setting changes write pacing and potential lag, not the five-minute autosave schedule itself.
What Minecraft autosave actually controls
Minecraft stores a world as many region and metadata files. Autosave periodically writes in-memory changes—block edits, entities, inventories, terrain and related world state—to those files. If the process or machine fails before a change is written, the server can restart with an older state. A shorter interval reduces that exposure but can create more frequent disk activity; a longer interval does the opposite.
The instructions here cover dedicated Java Edition servers running vanilla or Paper. Bedrock Dedicated Server behavior, command permissions and configuration names were not verified, so do not apply these steps to Bedrock without checking Microsoft’s current documentation.
#1 Best Overall
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
The default interval
Vanilla Java autosave runs every 6,000 ticks, approximately five minutes. A tick is the server’s normal 20-times-per-second simulation step, so 6,000 ticks divided by 20 equals about 300 seconds. The practical interval can vary slightly when a server is overloaded because delayed ticks also delay scheduled work.
| Item | Value | What it means |
|---|---|---|
| Vanilla autosave interval | 6,000 ticks | About five minutes under normal 20 TPS operation |
save-off |
Runtime switch | Stops normal level-file writes; changes are queued |
save-on |
Runtime switch | Re-enables normal level-file writes |
save-all |
Manual command | Writes current server data to disk |
save-all flush |
Manual command with flush | Saves immediately and can freeze the server briefly |
| Paper chunk-write cap | 24 chunks per tick by default | Controls how quickly Paper spreads autosave writes across ticks |
Commands for turning autosave off, on and forcing a save
Run commands in the dedicated server console, or in chat as an operator with the required permission. The save-off and save-on commands require permission level 4 and apply to dedicated servers. They are not a permanent configuration change: a server restart resets saving to its normal enabled state.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minutesave-off: pause level-file writes
Use:
save-off
This prevents the server from writing normal changes to level files while you copy them for a backup. Player, advancement and statistic files are exceptions. New level changes are held in memory and queued until saving is enabled again. Because queued changes still consume memory and remain vulnerable to a crash, leave saving disabled only for the time needed to complete the copy.
save-on: resume normal saving
Use:
save-on
Run this immediately after a backup or maintenance operation. Saving resumes and queued world changes can be written. If the server restarts while saving is disabled, the restart itself restores the normal enabled state, but any changes that had not been written before a crash can still be lost.
save-all: write data on demand
Use:
save-all
This requests a normal save and works even when automatic saving is currently off. Use it before planned maintenance, a controlled shutdown or a snapshot. The command may take time on a large world, and the console should report its completion.
Rank #2
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
save-all flush: force an immediate disk flush
Use:
save-all flush
The flush form forces data to be written immediately rather than waiting for ordinary write scheduling. It can freeze the server briefly while storage catches up, so run it during a quiet period and warn players first. A short pause is expected; a long pause or timeout indicates storage, world-size or hardware pressure that should be investigated.
Free tools Windows power users keep installed
One-click scans. No signup required.
Safe procedure for making a live world backup
Copying a running world while files are changing can produce an inconsistent backup. The following sequence minimizes that risk without stopping the server.
- Announce maintenance. Tell players that saving will pause and that a short freeze may occur during the flush.
- Pause level writes. Run
save-offin the server console. Confirm the console accepts the command. - Write the current state. Run
save-all flush. Wait for the save operation to finish before copying anything. - Copy the required data. Copy the server’s world directory and any configuration or whitelist files your recovery plan requires. Do not modify the original while copying.
- Verify the copy. Check that the copy contains the expected region files and that its size is stable. If your backup system supports checksums, compare the source and destination after the copy.
- Resume saving. Run
save-onas soon as the copy is complete. - Record the result. Note the backup time, world name and destination so you can identify the newest restorable copy.
Do not leave save-off active because a script failed silently. A watchdog, scheduled task or administrator should alert you if saving remains disabled longer than the planned maintenance window.
What you can and cannot configure on vanilla Java
Vanilla’s documented default interval is fixed at 6,000 ticks. The runtime save commands let you pause, resume or trigger a write, but they do not provide a built-in command for changing that interval to an arbitrary number. There is also no verified autosave entry in server.properties in the available Java references.
Community and Bukkit-based configurations show conflicting values for a bukkit.yml ticks-per.autosave setting—excerpts report 900, 6,000 and 0 as defaults. Because those values are unresolved and can depend on server software and version, do not assume one is correct for your installation. Check the documentation shipped with your exact server build before editing it, make a backup of the file, and test after every change.
Rank #3
- UNO Video Game Cards Set - Bundle with Minecraft, Super Mario, Teenage Mutant Ninja Turtles UNO Cards for Kids Plus Stickers, More | Minecraft, Mario, TMNT Activities for Kids, Family Game Night.
- This video game card game set comes with three deck of UNO cards featuring unique artwork from Mario Kart, Minecraft, and Teenage Mutant Ninja Turtles.
- Sure to be a hit with all video game fans, this collectible UNO card deck 3 pack is perfect to give your video game fan. Each UNO deck includes slightly different rules for endless fun!
- Play at your next family game night, these Super Mario, Minecraft, and TMTN editions of UNO each provide a new, fun twist on the classic card game. Great for the whole family.
- Officially licensed Minecraft, Mario Kart, and Teenage Mutant Ninja Turtles UNO card game set for kids and adults alike.
If you need a custom schedule on vanilla, use an external scheduler or a server extension only after verifying that it supports your Minecraft version. A scheduler that blindly runs save-all too often can increase disk load, while one that disables saving for long periods increases crash-related data loss. Keep the normal autosave enabled unless you have a tested operational reason to do otherwise.
Configuring autosave write pacing on Paper
Paper separates the timing of autosave work from the amount of chunk data written in an individual tick. The relevant setting is max-auto-save-chunks-per-tick. Paper’s documentation lists a default of 24 and says most servers can keep that default.
Global Paper world defaults
- Stop the Paper server cleanly before editing configuration.
- Open
config/paper-world-defaults.ymlin the server directory. - Find the
chunkssection. - Set
max-auto-save-chunks-per-tickto the integer you have chosen. - Save the file and start the server. Watch startup logs for YAML errors and confirm the setting is accepted.
A minimal structure is:
chunks:
max-auto-save-chunks-per-tick: 24Use spaces for YAML indentation. Do not add tabs, quote the number unnecessarily or place the key under an unrelated section.
Per-world overrides
To use a different cap for one world, place the setting in that world’s paper-world.yml. The global defaults file supplies the baseline; a per-world value overrides it for that world. This is useful when a resource-heavy survival world needs different treatment from a small lobby or minigame world.
Outdated 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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDo not follow obsolete paper.yml instructions
Older guides often tell administrators to edit paper.yml. Paper’s configuration was split in the 1.19-era layout. Current installations use paper-global.yml for global settings and paper-world-defaults.yml for world defaults, with paper-world.yml for an individual world’s override. The exact files present can vary by Paper version, so follow the layout generated by your running build rather than copying an old path.
Rank #4
- The cooperative Minecraft card game invites 2-4 players aged 8 and up to explore the picturesque landscapes of Minecraft and search for hidden treasures
- Experience Minecraft as a new, exciting adventure and fill your chests with treasures before you are caught by the monsters
- Only if you work well as a team and combine luck with strategy can you win the game together.
- The card game for 2-4 people is entertaining and varied, lots of fun and perfect for taking with you thanks to its practical travel format.
- The card game is perfect for every family or friends game night and a great gift for all small and big fans of Minecraft.
Choosing a Paper value without guessing
The setting is a per-tick write cap, not a “save every N seconds” interval. Lowering it spreads chunk writes over more ticks. That can reduce a sharp autosave spike on slow storage, but it also makes a save take longer to complete. Raising it can finish a save sooner, but more disk work in one tick can increase latency and cause visible lag.
| Observation | Likely action | Trade-off |
|---|---|---|
| No measurable autosave lag and normal storage latency | Keep the documented default of 24 | Least unnecessary configuration; write pacing remains Paper’s supported baseline |
| TPS drops or tick duration spikes during saves on slow storage | Test a lower value in a staging copy, then profile again | Smaller spikes may mean saves take longer overall |
| Storage is fast but a very low value leaves dirty chunks pending for a long time | Test a higher value cautiously | More writes in each tick can worsen latency |
| No evidence that autosave causes lag | Do not change the default | Unnecessary tuning can create a new bottleneck |
Community recommendations vary: some guides suggest 6–12 for slow storage, while others advise keeping 24 and profiling first. Those are opinions, not universal requirements. Measure tick duration, storage latency and player symptoms before changing the cap. Change one value at a time, keep the previous file, and test under a realistic player load.
Autosave interval versus Paper write pacing
These controls solve different problems. The interval determines how often the server begins its normal save cycle and therefore how much recent progress could be lost after a crash. Paper’s cap determines how aggressively chunk writes are distributed across ticks once saving work is being performed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Question | Vanilla save commands and interval | Paper chunk-write cap |
|---|---|---|
| Does it change the five-minute default schedule? | No command changes the documented vanilla interval; commands pause, resume or trigger saving | No; it limits chunks written per tick |
| Is it persistent after restart? | save-off is not persistent; restart restores normal saving |
Yes, when stored in the Paper configuration file |
| Primary use | Backups, maintenance and deliberate manual saves | Reducing or distributing autosave-related tick work |
| Main risk of an extreme setting | Long periods without writes increase recoverable-progress loss | Too low can leave writes pending; too high can create lag spikes |
Operational checklist for reliable saving
- Keep the server’s normal autosave enabled during ordinary play.
- Use
save-allbefore planned restarts or migrations. - Use the
save-off→save-all flush→ copy →save-onsequence for live backups. - After every restart, confirm that saving is on;
save-offdoes not survive a restart, but a failed maintenance script may still have left an administrator uncertain about the current state. - Store backups on different storage from the live world so a disk failure does not destroy both copies.
- Retain multiple dated backups rather than overwriting the only copy.
- Periodically test restoring a copy on a separate server. A backup that has never been restored is not a verified recovery plan.
- Monitor tick time and disk latency before tuning Paper’s chunk cap.
Troubleshooting common problems
The command is rejected or has no effect
Run it from the dedicated server console, check that you are an operator with permission level 4, and verify that you are using Java Edition. A command entered in a client without sufficient permission will not pause the server’s writes.
The backup contains a rollback
Make sure save-off was accepted, run save-all flush, and wait for completion before copying. If the server crashed or was killed while saving was off, queued changes may never have reached disk. Restore the newest known-good backup and investigate the shutdown rather than repeatedly copying an unflushed live directory.
Best Value
- STANDARD DECK: This deck of Minecraft cards features the iconic characters from the series on the faces of each card and a protective, giftable storage tin that any Minecrafter or card player will love
- COLLECTIBLE TIN: The cards come in a decorative storage tin in the design of the classic Minecraft icon, making them perfect for fans or gamers. Add some retro fun to your next poker night
- TRAVEL GAMES: Whether you like go fish, gin rummy, blackjack, poker, old maid or solitaire, this deck is perfect to bring along in the car or your purse so you are always ready to play
- NOVEL AND ORIGINAL: For those in the fandom looking for novelty items and all things geek, crazy, and unique, Paladone is your best source for top selling toys, mugs, collectibles, and novelties
- OFFICIALLY LICENSED: This quality collectable is a unique addition to any fan's set. Give this cool collector's merchandise to mums, dads, fans, grads, kids, guys, and gals who love pop culture fun
The server lags whenever autosave runs
First establish whether the lag coincides with autosave by comparing tick-time or TPS logs with save events. Check available disk space, storage latency and other jobs that run at the same time. On Paper, leave the default of 24 unless measurements show a problem; then test a lower or higher cap in a controlled environment and compare both peak tick time and total save duration.
Saving remains disabled after maintenance
Run save-on manually and verify that the console confirms it. Review backup scripts for error paths that skip the final command. Add a timeout or alert so an interrupted copy cannot leave the production server accumulating queued changes unnoticed.
Recommended Free Tools
An old tutorial names the wrong Paper file
Use the files generated by your current Paper build: paper-global.yml, paper-world-defaults.yml and, for a world-specific override, paper-world.yml. Do not create a legacy paper.yml merely because an older guide references it.
What happens if you disable autosave for too long
save-off is intended for a short, controlled copy operation—not as a permanent performance mode. World changes continue in memory, so a crash, forced termination or hardware failure can discard everything since the last successful write. Memory pressure can also increase as more changes remain queued. If your objective is to reduce lag, profile Paper’s pacing and storage instead of leaving saving disabled.
Recommended configuration by use case
| Use case | Recommended approach |
|---|---|
| Ordinary vanilla Java survival server | Leave the five-minute autosave behavior active; use save-all before planned restarts |
| Live backup while players remain connected | Run save-off, then save-all flush, copy the files, and immediately run save-on |
| Paper server with no measured save lag | Keep max-auto-save-chunks-per-tick: 24 |
| Paper server with measured save-related spikes | Profile first, test a different cap in a staging environment, and retain the original value for rollback |
| Server requiring a custom interval | Verify a version-compatible scheduler or extension; do not assume an unverified bukkit.yml default or a nonexistent server.properties key |
Limits of these instructions
The documented facts above apply to Java Edition vanilla and Paper configurations. The exact bukkit.yml autosave defaults reported by different excerpts are inconsistent, so no single default is stated here. Bedrock Dedicated Server autosave and save-all behavior were not verified. Always match commands and file paths to the server software and version shown by your own installation.
The Bottom Line
For Java servers, keep normal autosave enabled, use save-off and save-on only around a controlled backup, and force a completed write with save-all flush before copying. On Paper, leave the default 24-chunk-per-tick cap in place unless profiling demonstrates a real autosave bottleneck.
Quick Recap
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.
