Tying a Minecraft player to a Quavern account, and the routes the game servers call.
Find your code below — there are 7 of them. The digit between the letters and the dash says who can act on it: 1 is something you can change, 2 and 9 are Quavern's to fix, 3, 4 and 5 are decisions about access, 6 and 7 mean the service is in maintenance or has moved, and 8 points at the device or the network. QVBK uses 1, 2, 3, 7. The shape of a code is explained in How to read a Quavern support code.
Class 1 — Your request or your action
Check what you sent and the state of the account: the request itself, a quota, or the object it names. Correcting that and trying again is normally the whole fix.
QVBK1-1404 — link_code_invalid
What it means. Quavern refused the link code: the value received is not in the expected form, or it is not one Quavern issued.
What to do. Send the value exactly as it was given to you, with nothing added, trimmed or re-encoded.
QVBK1-1409 — player_already_linked
What it means. Quavern has not published what this code means. Its name does not settle it, and this page will not guess — indistinguishable from already_linked (QVBK1-2409) by its slug alone; the two must name different sides of the same link.
What to do. Quote the code to support at [email protected], with the time and what you were doing, and you will be told what it means.
QVBK1-2404 — not_linked
What it means. No link exists yet between the Minecraft player and the Quavern account, and this route only works once one does.
What to do. Create the link first, from the game or from the account page.
QVBK1-2409 — already_linked
What it means. Quavern has not published what this code means. Its name does not settle it, and this page will not guess — indistinguishable from player_already_linked (QVBK1-1409) by its slug alone; the two must name different sides of the same link.
What to do. Quote the code to support at [email protected], with the time and what you were doing, and you will be told what it means.
Class 2 — Quavern's server or one of its dependencies
Nothing you did caused it. Wait a moment and try again. If it keeps happening, send support the code and the time — that is what lets the incident be found in the logs.
QVBK2-1503 — quavblok_unconfigured
What it means. Quavblok has not been given the configuration this needs on this deployment, so the feature is switched off rather than half working.
What to do. Nothing on your side fixes this. Tell support, with the code and the time.
Class 3 — Authentication, authorisation or security
Sign in again, or ask whoever administers your organisation for the access this needs. Support will never work around an access control on your behalf.
QVBK3-1401 — server_key_invalid
What it means. Quavern refused the Quavblok server key: the value received is not in the expected form, or it is not one Quavern issued.
What to do. Send the value exactly as it was given to you, with nothing added, trimmed or re-encoded.
Class 7 — Stopped, moved, or an update is required
What you called has stopped, moved, or needs a newer version. Follow the migration or update notice rather than retrying.
QVBK7-1410 — link_code_expired
What it means. The link code was genuine, but its lifetime has run out.
What to do. Start the step again to obtain a fresh value. Do not resend the old one.
Still stuck
Write to [email protected] with the code, the reason, the time with its time zone, and the route you called. Never send a password, a token, an API key or full card details — support will never ask for any of them.
Quavern help reference: support-codes-qvbk/en