How LeviLauncher's Version-First Workflow Works

Updated

LeviLauncher treats each Minecraft Bedrock (GDK) installation as its own managed entry, so you install, rename, launch, and remove Release or Preview builds as separate setups rather than overwriting one shared install. That is the core of its "version-first workflow," and it is the reason the launcher is useful when you need to switch between different Bedrock versions on Windows. The approach fits anyone running more than one build — for example, keeping a stable Release for normal play while testing a Preview build alongside it.

What "version-first" actually means

Most launchers start from a single game install and let you point it at different profiles. LeviLauncher inverts that: the version is the primary object you manage, and everything else hangs off it.

Per the LeviLauncher documentation, the workflow covers four actions per build:

  • Install a Minecraft Release or Preview build
  • Rename it so you can tell your setups apart
  • Launch it directly
  • Remove it when you no longer need it

Each of these acts on one version entry, which keeps every setup "under control" and separate from the others.

Why isolation matters

The documentation highlights "clean isolation" as a design goal. In practice, that means one version's files, settings, and content do not bleed into another's. If you have ever had a mod or world edit break a second installation, the value here is obvious: a Preview build you are experimenting with cannot disturb the Release build you play on.

This is the main reason to choose a version-first launcher over manually juggling folders — the separation is built into how versions are stored, not something you maintain by hand.

Managing versions step by step

The general loop, based on the documented actions, looks like this:

  1. Install the build you want (Release or Preview). It becomes its own entry.
  2. Rename the entry to something meaningful — for example, "1.21 Release" versus "Preview test" — so you can identify it at a glance.
  3. Launch that entry when you want to play it. Because setups are isolated, launching one does not affect the others.
  4. Remove the entry when it is obsolete, freeing you from leftover files tied to a version you no longer use.

The expected result after each step is a distinct, self-contained version you can switch to without reconfiguring anything else.

Where the rest of the toolkit fits

Beyond version management, the documentation lists a content toolkit, mod-ready support, and world utilities. These attach to the version-first structure: content and mods belong to a specific build, and world utilities operate within that build's isolated environment. So the version you select determines which content, mods, and worlds are in play — another reason the version is the natural starting point.

When this workflow suits you

Choose a version-first launcher like LeviLauncher if:

  • You regularly move between Minecraft Bedrock Release and Preview builds
  • You want each build's mods, content, and worlds kept apart
  • You prefer managing versions as named, removable entries rather than one mutable install

If you only ever run a single Bedrock version and never touch Preview builds, the isolation and multi-version management offer less benefit — a simpler single-install setup may be enough.

For the exact install, rename, launch, and remove steps and any version-specific options, refer to the LeviLauncher user documentation, since the precise controls live there.