How to Enable Offline Mode on a Minecraft Server (Non-Premium / Cracked Players)

The short answer: three steps to offline mode

Your friends without a Minecraft account can join as soon as the server stops checking logins with Mojang. Three steps, about a minute:

1. Stop the server. Fully stopped, not restarted — a running server writes its own copy of the settings back over yours when it shuts down.
2. Open server.properties and set two lines. The file sits in your server's root folder, the same place as the server jar:

   online-mode=false
   enforce-secure-profile=false

   Both matter. On Minecraft 1.19 and newer, changing only the first one is not enough.
3. Save, then start the server. Non-premium players now connect on the same address as everyone else.

What offline mode actually does

When a player joins a normal server, the server asks Mojang's session servers: "is this really the account behind this username?" Mojang answers, the login is accepted, and the player's identity is proven. That is online mode, and it is the default.

Offline mode removes that question. The server accepts whatever username the client sends and never contacts Mojang at all. Nothing is patched, cracked or modified — you are flipping a switch that Mojang put in the vanilla server on purpose, because plenty of legitimate setups need it:

• LAN and event servers that run with no internet connection at all, where the Mojang check would fail for everyone.
• Networks behind a proxy, where BungeeCord or Velocity does the authentication once at the front door and the servers behind it must not repeat it.
• Isolated or firewalled environments — test servers, school and office networks, air-gapped machines.
• Playing with friends who have not bought the game yet, which is what most people are here for.

What it does not do is make the setting free of consequences. Verified logins are the thing standing between your server and someone typing your admin's username, so the default is online-mode=true for a good reason and that remains the right call for a normal public server — see why the default exists. This guide is for the case where you have decided you need it off, and the rest of it is about doing that without handing your server away.

Turning it on in the HytHost panel, step by step

There is no toggle for this in the panel's Startup tab — offline mode lives in the server's own config file, so you edit it directly. The whole job takes a minute:

1. Stop the server. Use Stop, not Restart. A running Minecraft server holds its settings in memory and writes them back to disk on shutdown, so an edit made while it is running gets silently overwritten. This is the single most common reason people think the change "did not save".
2. Open the Files tab. Your server's root folder is what you land on — the same place as server.properties, the plugins folder and the world folder.
3. Click server.properties to edit it. It opens in the panel's built-in text editor — a plain list of settings, one per line, in alphabetical order.
4. Find online-mode and set it to false. Change online-mode=true to online-mode=false. Do not add quotes, spaces around the equals sign, or a second copy of the line.
5. Find enforce-secure-profile and set it to false too. If the line is not in your file at all — common on older worlds created before Minecraft 1.19 — just add enforce-secure-profile=false on its own line at the end.
6. Save, then start the server. Watch the console as it boots. A line reading that the server is running in offline mode is your confirmation it took effect.

Security: in offline mode, anyone can be anyone

This is the section to read twice. Everything else in this guide is a config change; this is the part that decides whether your server survives being public.

What actually changes

With verification switched off, a username is no longer proof of anything — it is just a string the client sends. Anyone who knows your address can connect claiming to be you, or your co-owner, or your head moderator. And because most permission setups grant rights by name, an impersonator does not need to break in: the server hands them the rights on arrival. If you opped yourself by username, someone else typing that username arrives opped.

That is not a hypothetical. A public offline-mode address with no auth plugin is one of the easiest servers on the internet to take over, and the usual result is a wiped world and every rank reassigned. The fix is not complicated, but it is not optional either.

Install AuthMe Reloaded

An authentication plugin puts a password in front of every username. Players register once, log in each session, and the name becomes theirs — impersonation stops working because knowing the name is no longer enough. AuthMe Reloaded is the long-standing standard for this and works on Paper and Spigot.

1. Download the JAR from the official listing and drop it into your server's plugins folder — the same process as any other plugin, covered step by step in how to install Minecraft plugins.
2. Restart the server so the plugin loads and writes its default config.
3. Open plugins/AuthMe/config.yml and tighten the defaults. These four are the ones that matter most:

   settings:
     restrictions:
       timeout: 30
       maxRegPerIp: 2
       allowChat: false
     security:
       minPasswordLength: 8

   That gives players 30 seconds to log in before they are kicked, caps how many accounts one address can create, keeps unauthenticated players from talking in chat, and refuses trivially short passwords.
4. Tell your players the two commands. First join: /register with their chosen password twice. Every join after that: /login with that password. Until they do, they cannot move, build or chat.

Grant permissions by group, not by name

Op is an all-or-nothing switch tied to a username, which is exactly the wrong shape for an offline-mode server. Use a permissions plugin and give ranks to groups instead, so that even a successful impersonation does not come with console-level power attached. Our guide on real staff ranks beyond op walks through setting that up.

What your players notice: new UUIDs and missing skins

Two things change for everyone on the server the moment you switch, and both are much easier to handle before you flip the setting than after.

Every player gets a new identity

Minecraft identifies players by a UUID, not by their name. In online mode that UUID is issued by Mojang and belongs to the account. In offline mode there is no account to ask, so the server generates one from the username instead — which means the same player gets a completely different UUID depending on which mode the server is in.

To your server that is not the same person. Everything keyed to the old UUID is orphaned: inventories, ender chests, advancements, spawn points, plugin balances, homes, land claims and permission group assignments. The world itself is fine and nothing is deleted — the data is simply attached to an identity nobody logs in as any more.

There is a second consequence worth understanding: because the UUID is derived from the name, whoever types the name owns the data attached to it. That is the same impersonation problem from the section above, seen from the other side, and it is the other reason an auth plugin is not optional.

Skins stop loading

Skins come from Mojang's servers, tied to the verified account. No verification means no skin, so everyone appears as the default Steve or Alex. SkinsRestorer fixes it: install it like any other plugin, restart, and players set their own with /skin set followed by a username. On a proxy network install it on the proxy rather than on each server behind it.

Proxy networks: BungeeCord and Velocity

If you run a network — a lobby plus a survival server plus a minigame server, all behind one address — the picture changes, and it is worth being precise because this is where offline mode is most often configured badly.

On a network, the servers behind the proxy normally run with online-mode=false even when the network as a whole is fully premium-only. That is by design: the proxy performs the Mojang check once at the front door and then forwards the already-verified player onward. Repeating the check on each backend would fail. So a backend sitting at online-mode=false is not an offline-mode network — it is a normal, correctly configured one.

Whether your network is premium-only or open to non-premium players is decided at the proxy, in the proxy's own config file: config.yml for BungeeCord, velocity.toml for Velocity. On HytHost, proxies installed from the panel's Version tab are written with online mode enabled at the proxy, so that file is the one to edit — not the backends.

One more Velocity detail if you are running a non-premium network: enforce-secure-profile has a proxy-side twin called force-key-authentication in velocity.toml. Turning off the backend setting while leaving the proxy one on produces exactly the same symptom — players rejected at login for a reason the server logs describe as a profile problem.

Testing it, and fixing what breaks

The only test that counts is a real one: have a friend without a bought account connect to your address. If the console prints a line naming them as they join, it works. Everything below is what to check when it does not.

The change will not stick

Almost always one of three things. You edited the file while the server was running, and it overwrote your change on shutdown — stop it first, then edit. Or a reinstall, a version change or a modpack install laid down a fresh server.properties, in which case simply set the two lines again. Or you edited a different copy of the file than the one the server actually reads, which happens on setups with more than one server folder. For what it is worth, the panel itself does not rewrite these two lines at boot: it manages only the server's IP and port entries, so a saved change on a stopped server stays saved.

A plugin refuses to enable

A handful of plugins — mostly ones dealing with accounts, ranks or economies — check the server's mode on startup and refuse to load in offline mode, or warn loudly about it. Read the console message rather than guessing: some simply need a config option acknowledging offline mode, others genuinely depend on Mojang UUIDs and have an offline-friendly alternative. Anything that stores per-player data will want your auth plugin loaded first, so keep AuthMe near the top of your setup rather than adding it last.

Offline mode is a supported setting on a HytHost Minecraft server, and the panel gives you the file manager, console and one-click backups to change it safely and roll back if you do not like the result. If Minecraft is a game you keep coming back to, buying it is what keeps it being made — but that is your call to make, not ours to lecture about.