← Project index

Software / Game tools

General-Purpose
Minecraft Launcher

A general-purpose Minecraft launcher engineered around large modpacks, launch ownership, diagnostics, and a startup experience beyond the frozen window.

Active developmentIndependent third-party project

A clearer way through the wait.

The project focuses on the part between choosing a modpack and arriving in the game: validating the local environment, constructing a predictable launch, supervising the process, and making long startups understandable.

It is being developed as a general-purpose launcher rather than as a companion tied to a single modpack or server. Capabilities listed below are intentionally separated by maturity; this page does not represent a production release.

Move startup ownership one level higher.

The launcher grew from a practical Minecraft² problem: a very large modern modpack can spend well over a minute initializing before presenting a useful window, followed by substantial resource and model processing before the title screen becomes interactive.

Solving that experience entirely from inside a Fabric mod is fundamentally limited because much of startup has already happened before Fabric code can render anything. By owning the process lifecycle, the launcher can present and diagnose startup independently of Minecraft’s rendering state.

Development status

What exists—and what comes next.

01

Current / prototyped

Deterministic Vanilla and Fabric launch planning, Mojang and Fabric metadata resolution, Java/runtime validation, a launcher-owned resource cache, structured process execution, Windows process ownership, diagnostics and log capture, presentation-host architecture, and secure account-provider design.

02

Authentication phase

Microsoft system-browser OAuth is the intended design. Authenticated Minecraft launching is not being claimed as complete while Minecraft Services approval and authentication work remain in progress.

03

Planned

Large-modpack instance management, Modrinth content interoperability, cinematic and creator-submitted startup presentations, adaptive presentation quality, diagnostics and performance recommendations, reversible settings optimization, and additional mod-loader support.

Why the launcher needs API access.

A user signs into their own Microsoft account through Microsoft’s supported system-browser OAuth flow. The launcher then needs to verify Minecraft ownership or entitlement, retrieve the user’s Minecraft: Java Edition profile, and launch the game that user legitimately owns.

  • The launcher does not collect or receive Microsoft passwords.
  • Authentication is intended to occur in Microsoft’s system-browser experience.
  • It does not use another launcher’s credentials or client ID.
  • No client secrets, tokens, or private diagnostics are exposed by this site.