Incremental Player Save
Implements incremental player saving to smooth out MSPT spikes from saving player data to disk in PlayerManager.saveAllPlayerData()
About this Mod
Incremental Player Save
A mod to eliminate MSPT spikes caused by player data auto-save on Minecraft servers.
What It Does
Minecraft's auto-save calls net.minecraft.server.PlayerManager.saveAllPlayerData() once per save interval, writing every online player's data to disk in a single tick. On servers with many players or with a lot of player data, this can cause a large MSPT spike.
Incremental Player Save fixes this by spreading player saves across multiple ticks, saving a small batch of players per tick rather than all at once. This mod was inspired by Paper's incremental player saving feature.
Who This Is For
Install this mod if you see any of the following:
- Regular MSPT spikes every auto-save interval (default: every 6000 ticks / 5 minutes)
net.minecraft.server.PlayerManager.saveAllPlayerDataappearing in Spark profiler results during spikes
This mod targets only player .dat file writes. It will not reduce spikes from chunk saving or other auto-save work.
Configuration
All options are in the mod's config file in config/incrementalplayersave.json
| Option | Description | Default |
|---|---|---|
ticksBetweenSaveAttempts |
How often (in ticks) the mod checks which players are due for a save | 20 |
ticksBetweenSavesPerPlayer |
Minimum ticks between saves for any individual player | 6000 |
maxPlayersSavedPerAttempt |
Maximum number of players saved per attempt. Controls per-tick save cost | 3 |
enableDebugLog |
Log save actions to console | false |
Other Notes
Some optimization mods may include similar functionality. Use Spark to confirm whether
saveAllPlayerDatastill appears in your profiles before installing. On my server with many optimization mods like Lithium, none of them alleviated the tick spike caused by PlayerManager.saveAllPlayerData().net.minecraft.server.PlayerManager.saveAllPlayerData()isnet.minecraft.server.players.PlayerList.saveAll()in Mojang Mappings.
Available Versions
How to Install Incremental Player Save on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (26.1.2).
Install Mod
Open the mod browser in the dashboard and search for "Incremental Player Save". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
26.1.2, 1.21.11
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Incremental Player Save server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (26.1.2). You can switch loaders with one click in the panel.
Is Incremental Player Save compatible with fabric?
Incremental Player Save officially supports fabric for Minecraft 26.1.2, 1.21.11. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Incremental Player Save – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Incremental Player Save consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Incremental Player Save with just one click on your server.