What Clean Isolation Means in LeviLauncher

Updated

Clean isolation in LeviLauncher means each Minecraft Bedrock (GDK) setup you create is kept separate from the others. A version, mod configuration, or world setup you change in one instance does not overwrite or interfere with another. This matters most when you want to test a Preview build or a mod without putting your main installation at risk.

How the isolation works in practice

LeviLauncher is a desktop launcher for Minecraft Bedrock Edition (GDK) on Windows, and its documentation describes a version-first workflow: install, rename, launch, and remove Minecraft Release or Preview builds while keeping each setup under control. Isolation is the mechanism behind that control.

  • Separate setups per version. A Release build and a Preview build exist as distinct entries rather than replacing each other.
  • Separate mod environments. A mod-ready setup can carry its own mods, so enabling a mod in one instance does not change another.
  • Independent world utilities. World-related tools operate within the setup you are working in, so changes stay scoped to that instance.

The practical effect: when you launch a given entry, you get the version and content configuration attached to that entry, not a merged state from everything you have ever installed.

Why this is useful

The main benefit is risk containment. If you want to try a Preview build or an untested mod, you can do it in its own setup and leave your normal installation untouched. If the test goes wrong, you remove or reset that one entry instead of repairing your main game.

A concrete example: you keep a stable Release setup for everyday play and create a second setup for a Preview build plus a few mods. When the Preview build updates or a mod breaks, only that second setup is affected. Your Release setup still launches with the same version and content it had before.

What to check before relying on it

Isolation is only as good as how you use the entries. Two habits preserve it:

  1. Create a new entry for experiments rather than modifying your main one. Renaming entries helps you tell them apart later.
  2. Remove setups you no longer need through the launcher, so leftover instances do not accumulate.

The documentation covers how isolation is maintained and how the version-first workflow handles install, rename, launch, and removal. For exact steps and any limits on what can be isolated, refer to the LeviLauncher user documentation at levilauncher.levimc.org, since behavior can differ between builds.