multimc/launcher

★ 4,625C++Audience · generalComplexity · 2/5LicenseSetup · easy

Mindmap

mindmap
  root((MultiMC))
    What it does
      Minecraft launcher
      Isolated instances
      Multi-version support
    Features
      Separate mod lists
      Per-instance settings
      Version management
    Tech stack
      C++
      Qt framework
    Use cases
      Modpack management
      Version testing
      Clean vanilla install

mindmap root((MultiMC)) What it does Minecraft launcher Isolated instances Multi-version support Features Separate mod lists Per-instance settings Version management Tech stack C++ Qt framework Use cases Modpack management Version testing Clean vanilla install

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Run a vanilla Minecraft instance and a heavily modded instance on the same computer without them sharing files

USE CASE 2

Keep separate instances for different modpacks or game versions so switching between them is clean and predictable

USE CASE 3

Build MultiMC from source to test or contribute a code change before submitting it

USE CASE 4

Help translate the MultiMC interface into another language via the Crowdin project

Tech stack

C++Qt

Getting it running

Difficulty · easy Time to first run · 5min

Download the pre-built release for your platform, building from source requires registering a separate Microsoft app for login to get a functional launcher.

Use and modify the source code freely, but the MultiMC name, logo, and branding are not covered by the license and cannot be used in custom builds.

In plain English

MultiMC is an alternative launcher for Minecraft that is designed for people who want to run multiple separate Minecraft installations on the same computer without them interfering with each other. The official Minecraft launcher stores everything in one shared location, which makes it difficult to keep different sets of mods or different game versions cleanly separated. MultiMC solves this by letting you create isolated instances, each with its own settings, mod list, and version of the game. The project focuses on predictability and long-term stability rather than adding new features. The README explicitly says the team is not looking for flashy additions, and contributions are expected to fit within the existing approach without disrupting it. The source code is available under the Apache 2.0 license, but the README is careful to note what the license does and does not grant. The MultiMC name, logo, and branding are not covered by the license. API tokens needed to connect to services the launcher uses are also not included. Anyone who builds the code from source will get a version called DevLauncher by default, not MultiMC. Distributing custom builds requires registering a separate app with Microsoft to handle login, because Microsoft's identity platform imposes restrictions on how applications can authenticate users. Translations for the interface are managed through a Crowdin project rather than through direct code contributions. Build instructions are in a separate BUILD.md file in the repository. Contributors are asked to discuss changes on the project's Discord server before submitting code. The project has been maintained since 2013 and is licensed under Apache 2.0.

Copy-paste prompts

Prompt 1

Walk me through creating two MultiMC instances: one for vanilla Minecraft 1.20 and one for a Forge 1.16.5 modpack, keeping them completely separate.

Prompt 2

How do I install and manage mods for one specific MultiMC instance without affecting any of my other Minecraft installations?

Prompt 3

I want to build MultiMC from source on Linux. Walk me through the steps described in BUILD.md and explain what DevLauncher is versus the official MultiMC build.

Open on GitHub → Explain another repo

← multimc on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.