SUPPORT CENTER
Find the answer. Keep playing.
Troubleshooting, error-code context, known issues, security guidance and bug reporting should connect in one support experience instead of sending players through disconnected systems.
Start with the error code.
Context connects troubleshooting to the right subsystem.
Authentication subsystem
GET HELP
Choose the right path.
Support, bugs, security and feedback are different workflows. The site should make that distinction clear before you submit anything.
Error codes
Understand a stable Leviathan error code and find relevant troubleshooting.
Look up a code →?Troubleshooting
Public launcher guidance for common setup and repair problems.
Open guide →BUGBug reports
Use public issues for reproducible defects that do not contain sensitive data.
Open issues →◇Security
Use the security guidance for vulnerabilities or sensitive findings.
Security guidance →ERROR CODE LOOKUP
One code, useful context.
The public error database is not connected yet. The interface below validates Leviathan-style codes without inventing explanations.
Enter a code to check its format.Public diagnostic content will be connected when the support database is ready.
SUPPORT ARCHITECTURE
Private support stays private.
Account, purchase, entitlement, recovery and other user-specific issues belong in a private support workflow. Reproducible product defects can be promoted or linked to a public bug record without exposing private data.
AcknowledgedSubmission received
NotifyIn reviewAssigned and investigated
TrackLinked to fixBug, version or article attached
UpdateResolvedResolution and next steps sent
CloseNeed community help?
Join the Leviathan Discord for community discussion while formal support systems continue to be built.