LEVIATHAN
Download

ARTICLES & GUIDES

Understand the platform.
Use it with confidence.

Practical explanations for Minecraft identity, capes, account linking, verification, privacy and troubleshooting. Technical reference material stays in Documentation, while these articles focus on everyday use.

Technical documentation →Support Center

START HERE

Popular Leviathan guides.

Each guide links directly to the relevant tool or setting so you can move from explanation to action.

Capes6 min

How cape discovery works

Learn what Leviathan can observe, what it cannot prove, and why ownership can show as Not confirmed.

Read guide ↓
Accounts5 min

Linking a Minecraft profile

Understand Microsoft authentication, Minecraft ownership verification and the difference between a Leviathan account and a Minecraft profile.

Read guide ↓
Profiles4 min

Verification, ranks and badges

See how notable verification, account ranks and Minecraft ownership signals stay separate.

Read guide ↓
Support5 min

Choosing the right help path

Know when to open private support, report a reproducible bug, submit feedback or use the public forum.

Read guide ↓
Security5 min

Protecting your Leviathan account

Use linked sign-in methods, 2FA, privacy controls and safe account recovery without sharing secrets.

Read guide ↓
Diagnostics4 min

Reading Leviathan error codes

Understand the stable code, crash or correlation ID, and the original external error that may accompany a failure.

Read guide ↓
CapesGuide

How cape discovery works.

Leviathan records cape textures observed on Minecraft profiles and combines those observations with curated cape metadata. The archive can show an official cape name, release context, type, observed wearer count, acquisition guidance and trusted references.

An observed wearer count is not the same as an official global owner count. Likewise, a linked profile may own a cape that Leviathan has not observed recently. That is why the ownership state uses Owned when there is evidence and Not confirmed when there is not enough evidence.

Open Cape ArchiveHow to get a cape
360CAPE VIEW

ACCOUNT LINKING

One account, verified connections.

Leviathan separates your platform account from external identities so each connection has a clear purpose.

1

Create or sign in

Use a supported Leviathan sign-in method such as email, Google or Microsoft. Multiple methods can belong to the same Leviathan account.

2

Verify Minecraft ownership

Use your own Microsoft and Minecraft authentication flow. Leviathan never asks for a Microsoft password in Discord or on a support ticket.

3

Link the profile

The verified Minecraft UUID becomes a trusted connection to your Leviathan account. Re-verification and safe unlinking remain separate from public profile display.

Manage accountProfile directory

PROFILE SIGNALS

Verification is not ownership.

Leviathan deliberately avoids one badge meaning several unrelated things.

Leviathan Verified

Notability

A manually granted badge for notable community members. It is not awarded automatically for email verification or profile claiming.

Linked Minecraft

Ownership

Shows that the Leviathan account completed the supported Microsoft and Minecraft verification flow for that profile.

Rank

Account entitlement

Ranks belong to the Leviathan account. A user can choose an eligible visible rank without changing the underlying Minecraft profile.

SupportRouting

Choose the right help path.

Support is private and is the right place for account, installation, purchase, entitlement, recovery and personal troubleshooting. Bug reports are for reproducible product defects. Feedback is for ideas and voting. The forum is for public discussion, tips and community questions that do not expose private information.

Support CenterFeedbackForum
?RIGHT PATH

ACCOUNT SECURITY

Keep secrets out of public channels.

Leviathan support and verification should prove access without asking you to expose credentials.

Use 2FA

Enable authenticator-based two-factor authentication where available and store recovery codes somewhere separate from your normal device.

Review connections

Keep only sign-in methods and linked profiles you still control. Re-verify ownership when a sensitive action requires fresh proof.

Never share tokens

Do not paste Microsoft access tokens, refresh tokens, XSTS tokens, passwords or recovery codes into Discord, the forum or a public bug report.

Security guidancePrivacy
DiagnosticsLVT codes

Read an error without losing the original cause.

A stable Leviathan error code identifies the subsystem and failure class. A separate crash or correlation ID points to one incident. When an external service, Java runtime or operating system provides its own status or exit code, Leviathan should preserve that information instead of replacing it.

When contacting support, include the Leviathan error code first if one is shown. Add screenshots or logs when useful, but remove secrets before sharing them.

Browse error codesGet help
LVTERROR CODE