Skip to content

How to make your Minecraft server cracked (offline mode)

Managed from: GamePanel. Updated 7 November 2026.

Set online-mode=false in the server.properties file (GamePanelFiles), with the server stopped, then restart it. Players without an official Minecraft account can then connect. Also install an authentication plugin, otherwise anyone can take someone else's username. This only applies to Minecraft Java: Bedrock doesn't have this setting.

In the GamePanel

your serverFilesserver.propertiesOpen
  1. In the GamePanel, stop the server.

  2. Open GamePanelFilesserver.properties.

  3. Replace online-mode=true with online-mode=false. From 1.19.1 onward, also set enforce-secure-profile=false.

    server.properties file open in the GamePanel, with the online-mode line highlighted
    server.properties file open in the GamePanel, with the online-mode line highlighted
  4. Click "Save File", then start the server.

  5. On Paper or Spigot, install an authentication plugin (AuthMe Reloaded or nLogin): each player sets a password on their first connection (/register), then enters it every time after (/login). See install a plugin. A Vanilla server doesn't accept plugins: switch to Paper first.

  6. Network with a proxy (Velocity or BungeeCord): cracked mode is set on the proxy (online-mode = false in velocity.toml, online_mode: false in BungeeCord's config.yml). All servers on the network should switch to online-mode=false with forwarding enabled (Velocity: modern forwarding, same secret key in config/paper-global.yml; BungeeCord: bungeecord: true in spigot.yml), and the authentication plugin goes on the proxy.

Common errors

  • "Lost" inventories and progress: in cracked mode, a player no longer has the same identifier (UUID) as in official mode. Players who already played start from scratch. Switch to cracked mode as soon as you create the server if possible. To get them back: inventory lost after a restart.
  • Impersonated usernames: without an authentication plugin, anyone can connect with an operator's username and take their permissions.
  • Chat errors or disconnects on the first message: enforce-secure-profile is still set to true.
  • "Failed to verify username" despite the change: the file wasn't saved, or the server wasn't restarted.

Can't find it? Open a ticket from your client area. Terms and conditions: helloserv.fr/en/legal