Dungeon Train Backup
Anyone who has played a heavily modded Minecraft world knows the sinking feeling. You update your modpack, launch the game, and your carefully built progress is gone because the launcher quietly replaced the config folder. Dungeon Train Backup exists to stop that from happening. It is a small but genuinely useful add-on that moves a mod's player data out of harm's way, keeps rolling zip backups, and gives you a one-click path back if an update goes wrong.
What Dungeon Train Backup Actually Does
At its core, this is a data safety net. When a modpack updates, most launchers overwrite the config/ directory, and any player data stored inside it disappears. Dungeon Train Backup relocates that data outside the danger zone, then maintains rolling zip backups both inside and outside your game instance. If an install ever turns up empty, a card appears on the title screen offering to put everything back with a single click.
The tool was built for Dungeon Train, but it is not locked to it. Any mod that registers with it gets the same protection, and there is no hard dependency on Dungeon Train itself. That flexibility makes it worth considering even if you only occasionally touch modpacks.
Restores Are Add-Only
One design decision stands out: restores only ever add files. They never delete or overwrite your existing data. That means a restore is a low-risk operation, which matters when you are recovering from a failed update and do not want to make things worse.
Supported Versions and Loader
Dungeon Train Backup currently targets NeoForge 1.21.1. If you are running a modern NeoForge pack on that version, you are in the right place. The source is openly available on GitHub, so you can verify exactly what the mod does before trusting it with your world data.
Settings and Configuration
Configuration is refreshingly simple. In the host mod's Options menu you will find two settings:
- Keep backups — choose On, Instanced, or Off depending on how aggressively you want backups stored.
- Backups per version — control how many rolling backups are retained.
Prefer editing files directly? The same options live in config/dungeonbackup-client.toml. Server administrators can disable backups entirely by launching with -Ddungeonbackup.backups=off.
If you would rather skip manual file placement, the foxygame.net launcher makes installing Dungeon Train Backup a one-click affair, pulling the correct build straight from its curated add-on catalog and handling version compatibility for you.
Commands for Manual Control
Two commands give you direct control when you need it:
/dungeonbackup backup— create a backup on demand./dungeonbackup restore [n]— restore a specific backup, or the most recent one.
These are handy before a big modpack change, or when you want a safety checkpoint without waiting for an automatic cycle.
How to Install Dungeon Train Backup
Installation follows the standard NeoForge routine. Download Dungeon Train Backup for Minecraft 1.21.1 from the project's GitHub releases, drop the jar into your mods folder, and launch the game with NeoForge selected. No extra dependencies are required. If you use a launcher with an add-on catalog, you can often install it without touching the filesystem at all.
Once loaded, check the host mod's Options to confirm backups are enabled and set your preferred retention count. Then play as normal — the mod works quietly in the background.
Why It Is Worth Having
Modpack updates are one of the most common ways players lose progress, and most of us only think about backups after something breaks. Dungeon Train Backup flips that around by automating the whole process: relocating data, rolling zips, and a title-screen recovery card that removes the panic from a bad update. Whether you are deep into a Dungeon Train run or just want insurance for any registering mod, it is a small addition with a big payoff. Grab it, set your backup count, and stop worrying about the next pack update.