Launcher core
Instances, version handling, loaders, runtime management and reliable launch flows.
ROADMAP
Build the core.
Then connect the ecosystem.
The roadmap separates what is actively being built from what is planned for later. Concepts are not presented as released features.
Development map
From launch to platform.
Status is intentionally conservative.
CURRENT PRIORITYLauncher foundation
Reliability · migration · runtime · release engineering
NOWCore
NEXTConnect
LATERExpand
NOW
Make the launcher dependable.
The current foundation work is about making launch, migration, compatibility, diagnostics and updates trustworthy before adding more surface area.
Migration
Import compatible worlds, mods, packs, shaders, settings and screenshots with preview, conflict handling, backup and rollback.
System detection
Conservative hardware-aware memory, Java and performance recommendations with clear user override.
Diagnostics
Stable error codes, crash correlation, download context and privacy-safe diagnostic bundles.
Release engineering
Checksums, staged releases, updater reliability, rollback and platform-specific validation.
Website & support
Clear product information, status, troubleshooting and public development communication.
NEXT
Connect the launcher and client.
Once the foundation is dependable, Leviathan can make settings, profiles, identity and diagnostics feel coherent across product surfaces.
Client foundation
Performance controls, HUD profiles, accessibility, customization and compatibility-focused client features.
Verified identity
Secure Minecraft ownership verification, profile linking and privacy-controlled public identity.
Support lifecycle
Private support tickets connected to public bug records, knowledge-base articles, releases and user notifications.
Content experience
Mods, modpacks, resources and compatible content organized around versions, loaders and instances.
LATER
Grow the ecosystem carefully.
These areas are direction, not release promises. Each should arrive only when its underlying identity, moderation, privacy and operations are ready.
Profiles & social
Verified public profiles, selected presence, friends and account-linked experiences with privacy controls.
Cosmetics
Capes, companions, themes and profile flair with clear ownership and availability states.
Server ecosystem
Discovery, compatibility metadata and community-facing integrations.
Localization
Crowdin-style translation, review, terminology, progress and quality workflows.
Mobile & notifications
Companion surfaces and useful lifecycle notifications where they add real value.
Commerce
Future store and entitlement systems only after secure account, ownership and fulfillment infrastructure is ready.
ROADMAP RULES
Status should mean something.
Roadmap labels are useful only if users can trust them.
AvailableReady for the public surface where it is shown
RealDevelopmentActively being built or validated
ActivePlannedDirection with no release date implied
FutureConceptExploration that may change or never ship
ExploratoryFollow development in public.
The public repository remains the detailed source for roadmap, changelog and technical documentation.