Balm in Launcher-Managed Modpacks

Avoid conflicting manual changes in an instance maintained by a launcher. Learn more about Balm Mod.

Understand who manages the files

A managed pack can have an expected file list and an update process controlled by its launcher. Before adding Balm manually, inspect the dependency information and the manager's installation result. A missing dependency may come from an incomplete installation or a mismatched pack release, rather than a need to replace individual files without checking the pack's intended configuration.

Use a test copy

Back up or duplicate the instance before making a manual adjustment. Record the original pack release and the files you change. Where possible, use the manager's repair or update workflow for that exact pack. An independently selected newer dependency may not match the other files or may later be replaced by the manager.

Document any deviation

If you maintain a custom variation, state clearly which pack release it began with and which dependencies changed. Test startup and the affected features in that variation. Keep a path back to the original instance. When reporting a problem, disclose the changed files so maintainers can distinguish the published pack from the modified local setup.