Skip to main content

Sign in: official and offline

GPCL supports two ways to sign in, and you can switch at any time. Offline sign-in needs no network, but you cannot join servers that require a verified account.

Offline sign-in​

Type a player name on the launch page and you can start; no password needed. The last 5 names you used stay in the dropdown and can be deleted one by one.

  • Suitable for single-player, LAN play, and servers without account verification.
  • No online verification, so it works without a network connection.
  • You cannot join servers with account verification enabled; you will be kicked.
  • Do not use someone else's official ID: both servers and other players can mistake you for them.

Microsoft sign-in​

  1. Click "Microsoft sign-in" on the launch page.
  2. GPCL opens your default browser and goes to the Microsoft sign-in page.
  3. Sign in and approve the authorization; the browser tells you that you can return to the launcher.
  4. GPCL receives the result automatically, and the player name comes from the account.

Sign-in waits up to 2 minutes. If nothing happens, first confirm that you finished signing in and authorizing in the browser, then check your network.

The launcher keeps you signed in, so you do not need to sign in again next time. "Optimize memory before launch" does not clear the sign-in state either.

Choosing between the two​

ScenarioUse
Single-player, playing on your ownEither
Server with account verificationMicrosoft account required
Server without account verificationEither
No networkOffline

Switching accounts​

While signed in with a Microsoft account, clicking the Microsoft button again signs you out, after which you can switch to an offline name. While offline, clicking Microsoft sign-in goes straight into the Microsoft flow.

Server says Invalid session​

Usually the sign-in state has expired, or the account does not own that version:

  1. Sign out and sign in with the Microsoft account again;
  2. Confirm that the account really owns this Minecraft version;
  3. Try a different verified server to rule out a problem with one server.