FREQUENTLY ASKED QUESTIONS

Clear answers.
No guesswork.

Leviathan is still under private development. This page explains availability, authentication, licensing, accounts, mods, privacy and the difference between public documentation and a public release.

Knowledge Base

Current project facts.

Based on public Leviathan documentation

PROJECT STATUSPrivate Development

No official public launcher builds are available yet.

PUBLIC BUILDNo
OWNERSHIPRequired
LICENSEProprietary

KNOWLEDGE BASE

What players should know today.

These answers reflect the current private-development state. Final pricing, release dates and some planned features have not been announced.

Is Leviathan Launcher available to download?
No. There is currently no official public launcher build, public beta, or release package. Development builds are restricted to authorized maintainers. The Download page will become the canonical release location when a real public build exists.
When will Leviathan Launcher release?
There is no announced public release date. A public release should happen only after release, security, authentication and compatibility gates are considered ready. You can follow the website roadmap, changelog and status page.
Does Leviathan require a legitimate Minecraft account?
Yes. Leviathan is intended for players who legitimately own or otherwise have valid access to Minecraft: Java Edition. Ownership or entitlement is intended to be verified through Minecraft Services.
Does Leviathan support cracked accounts or authentication bypasses?
No. The project does not provide cracked authentication, ownership bypasses, license bypasses, account impersonation or circumvention of Microsoft or Mojang security systems.
How does Microsoft login work?
The intended authentication chain uses Microsoft authentication, Xbox Live authentication, XSTS, Minecraft Services authentication, Minecraft ownership verification and Minecraft profile retrieval. Leviathan does not ask for or directly store your Microsoft password.
What is the Minecraft AppID status?
The Leviathan Launcher Minecraft AppID review has been approved. That approval does not mean production authentication is fully validated or that public builds are available. Production testing remains a separate release requirement.
Why is the GitHub repository public if the launcher is private?
The public repository exists for project information, documentation, development transparency, security and licensing information, review, and future organization. Public documentation does not mean public binaries are available.
Is Leviathan open source?
No. Leviathan Launcher is proprietary software. Public repository visibility does not grant general permission to copy, redistribute, modify, repackage, sell or sublicense original Leviathan Launcher materials. See the public repository license for the complete terms.
Is Leviathan free?
No public release exists yet, so final pricing and monetization details have not been announced. Any future pricing, free features, optional cosmetics or commercial features should be documented before public release.
Will Leviathan support mods and content?
Mod and content integration is planned. The broader product direction includes mods, modpacks, resource packs and shaders, with compatibility-aware management and integration with third-party ecosystems where appropriate.
Will Leviathan have profiles and cosmetics?
Multiple launcher profiles and cosmetic systems are planned. Profiles may eventually combine Minecraft versions, loaders, Java versions, memory settings, mods, resource packs, shaders and other launcher settings. Cosmetic details remain subject to development changes.
Does Leviathan see my Microsoft password?
No. Users authenticate through Microsoft’s own authentication infrastructure. Leviathan is not designed to ask for, receive or store Microsoft account passwords directly.
Does Leviathan collect analytics?
There is currently no public Leviathan Launcher telemetry or analytics program. If telemetry, crash reporting or analytics are introduced later, the project privacy documentation should be updated before or alongside those features.
How should I report a security issue?
Use the Security page and the repository security guidance. Never post passwords, access tokens, refresh tokens, session cookies, private keys, client secrets or other sensitive credentials in a public issue.

Still looking for an answer?

Use the Support Center for troubleshooting and public bug-report guidance, or follow development through the public repository.