DEVELOPMENT BLOG

What we are building,
and why.

Product decisions, implementation notes and progress across Leviathan. This is where larger changes get context beyond a short changelog entry.

Minecraft dataSeptember 14, 2026

Building the Leviathan Cape Archive.

Capes are more useful when the page explains more than a texture. The new archive combines official cape names, release context, acquisition guidance, observed wearers, type-aware rarity, ownership checks for linked profiles, multiple preview modes and trusted references.

The design keeps a clear distinction between official cape history and Leviathan's own observations. When ownership cannot be proven from available data, the interface says Not confirmed instead of pretending it knows more than it does.

CPCAPE ARCHIVE

RECENT NOTES

Inside the platform.

Longer explanations for systems that connect the website, accounts and Minecraft identity.

AccountsSep 14, 2026

One connected Leviathan account

Email, Google and Microsoft sign-in should lead to one account identity. Minecraft linking then verifies the game profile separately, keeping authentication and Minecraft ownership as distinct concepts.

Open account dashboard →
ProfilesSep 14, 2026

Verification should mean one thing

Leviathan Verified is reserved for notable community members selected by staff. Email verification, linked Minecraft ownership and public profile claiming remain separate signals instead of sharing one badge.

Browse profiles →
PlatformSep 14, 2026

Why API Lab is staff-gated

Single read-only diagnostics are useful, but batch checks can create unnecessary load. Leviathan separates regular diagnostic access from staff batch operations and applies deliberate cooldowns.

Open API Lab →
CommunitySep 14, 2026

Community is becoming a first-class surface

The site now has a real forum, structured feedback, creator and localization paths, a development blog and an article library instead of sending every kind of conversation to the same channel.

Open forum →
SupportSep 14, 2026

Support, bugs and feedback stay separate

Private support cases, reproducible product defects and public suggestions need different privacy rules and workflows. Leviathan routes each path separately while allowing staff to link related records.

Support Center →
DiagnosticsSep 14, 2026

Error codes as a support bridge

Stable Leviathan error codes are designed to connect launcher failures, logs, known issues and remediation without replacing the original exception, exit code or service error.

Browse error codes →