AstroAutoSave
v1.0.01.20+AstroAutoSave performs configurable auto-saves on your server with optional broadcast warnings before each save. Per-world toggle supported.
Overview
A server crash or power loss can roll the world back to whenever it was last written to disk, which on a default setup may be longer ago than you would like. AstroAutoSave gives you direct control over that window by saving your worlds on a fixed interval you choose, so the most a crash can cost is the time since the last save rather than the time since the last restart.
Because a world save can cause a brief hitch on a large or busy server, the plugin can broadcast a short warning before each save so players know a momentary pause is coming and is normal, not a sign of a problem. The warning and completion messages are fully customisable, and you can scope saving to specific worlds or leave it on all of them with a wildcard, which is useful if you want to spare a large, rarely changing world from frequent writes.
It also adds a manual trigger. /autosave now forces an immediate save, which is exactly what you want before a planned restart, a backup run or risky administrative work, so you can guarantee everything is on disk at that moment. The whole plugin is intentionally small and dependency-free, doing one job reliably rather than bundling features you would have to configure around.
Who it is for
Any server that wants a tighter, predictable save window against crashes, admins who save manually before restarts or backups, and large worlds where you want to control which worlds save and warn players about the brief save pause.
Features
- Configurable save interval (default 5 minutes)
- Broadcast warning before save
- Per-world enable/disable
- Manual save command
- Lightweight and reliable
Commands
| Command | Description | Permission |
|---|---|---|
/autosave | View plugin info | astroautosave.command |
/autosave reload | Reload config | astroautosave.reload |
/autosave now | Trigger manual save | astroautosave.now |
Permissions
| Node | Description | Default |
|---|---|---|
astroautosave.command | View autosave info | true |
astroautosave.reload | Reload config | op |
astroautosave.now | Manual save | op |
Example Config
# AstroAutoSave Configuration
interval-minutes: 5
warning-before-seconds: 10
worlds:
- "*"
messages:
warning: "&e&lAutoSave &8| &7Saving in %seconds% seconds..."
complete: "&e&lAutoSave &8| &aSaved %count% world(s)."interval-minutes sets how often worlds are saved (5 is every five minutes). warning-before-seconds controls how far ahead the warning broadcast fires; set it to 0 to save silently. The worlds list accepts specific world names or '*' for every world, so you can include or exclude individual worlds. The messages section customises the warning and complete lines, with %seconds% and %count% placeholders.
Installation
Drop AstroAutoSave.jar into /plugins and restart. It has no dependencies and begins saving on the default interval immediately, generating a config.yml you then tune. Note it saves worlds to disk on a schedule; it does not copy files off the server, so pair it with a real off-site backup process for true disaster recovery.
Download
Frequently Asked Questions
Is this plugin a backup system?
Not on its own. AstroAutoSave forces your worlds to be written to disk on a schedule, which protects against losing recent progress in a crash, but the files still live on the same server. For true disaster recovery, combine it with an off-site backup process that copies those saved files somewhere safe. The plugin makes sure the data on disk is fresh; a backup tool makes a copy of it.
Will auto-saving cause lag?
Saving a world can cause a brief hitch on large or busy servers because the data has to be flushed to disk. That is why the plugin can broadcast a warning beforehand so players expect the momentary pause. On smaller servers the effect is usually unnoticeable. You can tune interval-minutes to balance freshness against frequency.
Can I save only certain worlds?
Yes. The worlds list in the config controls which worlds are saved. Use '*' to save every world, or list specific world names to limit saving, which is useful for excluding a large, rarely changing world from frequent writes while still protecting your main survival world.
How do I force a save before a restart?
Run /autosave now to trigger an immediate save of the configured worlds. Doing this right before a planned restart, a backup or risky admin work guarantees everything is on disk at that point, so nothing since the last scheduled save is at risk.
How do I turn off the warning message?
Set warning-before-seconds to 0 in the config and the plugin will save silently without broadcasting a heads-up. Otherwise it broadcasts the warning that many seconds before each save, using the customisable message in the messages section.
Does it work with multiple worlds and Multiverse?
Yes. It saves any worlds that are loaded on the server, including those created or managed by a multi-world plugin, as long as their names are covered by the worlds list (or you use the '*' wildcard). It saves loaded worlds by name and does not depend on how they were created.