How to Back Up a Balm Mod Instance

Protect your worlds and configuration before changing a Balm-dependent modpack. Learn more about Balm Mod.

Choose what to preserve

Close the game and launcher before copying an instance. Preserve saves, configuration, the active mods folder and any launcher profile information needed to identify the setup. Record the Minecraft and loader versions separately: a folder of JARs does not explain which profile should load them. Keep the backup outside the live instance so it cannot be mistaken for an active mod directory.

Check your recovery copy

Open the backup location and confirm the expected saves and configuration files are present. Give it a meaningful date and profile name. Where your launcher supports instance duplication, use a separate test copy for experiments. Test the copied setup before changing the original, and avoid opening your only important world to check an unfamiliar dependency combination.

Restore a complete working set

If an update fails, restore the matching mod files and configuration together. Restoring only Balm while leaving a newer dependent mod installed can leave the same unmet requirement. Keep the failed test separate if you need its logs, and return to the version record that accompanied the successful backup.