Skip to content

Backups and Recovery

Innectic edited this page Nov 9, 2026 · 1 revision

Backups and recovery

Deletion and regeneration retain the original world folder under:

plugins/Dimensify/backups/<world>-<timestamp>-<id>/

This happens after player evacuation and a successful unload. Dimensify does not permanently erase that backup. These archives cover the world folder; they are not scheduled backups of the database, configuration or inventory-group snapshots.

Restore an archived world

  1. Stop the server.
  2. Keep any current world folder separate if you intend to retain it.
  3. Move the chosen backup into the server's world container under the desired valid world name.
  4. Start the server.
  5. If the world was deleted or unregistered, import it with the correct environment and optional generator.
/dimensify import survival normal
/dimensify import survival_nether nether
/dimensify import custom normal Terrain:mountains

After regeneration, the original registration and configured settings remain. Restoring the old folder does not restore an earlier copy of those settings automatically; restore the matching worlds.yml when needed.

Deleting or unregistering a world cleans up related named portals, anchors and dimension links. Restoring its folder does not recreate those registrations. Reconfigure them or restore a matching plugin-data backup.

Back up a complete server state

With the server stopped, retain:

  • The world folders, including normal Minecraft player data.
  • plugins/Dimensify/config.yml and worlds.yml.
  • The configured SQLite database, MySQL database, or flat-file storage.yml.
  • plugins/Dimensify/players/ when inventory groups are used.
  • Custom generator plugins, their settings and any required datapacks.

Restore matching world and player-group data together. Loading inventory snapshots from a different point in time can restore a different set of items than the Minecraft player data.

Failed operations

A failed unload leaves the world registered. A failed clone retains its partial destination folder for inspection; move that folder away before retrying with the same name.

Regeneration attempts to restore the original folder if generation fails. Its error identifies the original backup path if recovery needs attention. Check the server log before retrying.

Malformed YAML and player snapshots are rejected. Keep the affected file for recovery rather than replacing it with an empty file.

See World Management for the differences between remove, delete and regen.

Clone this wiki locally