Minecraft server.properties Essentials on GlassHosting

What server.properties actually controls

On a Minecraft Java server, server.properties is the plain-text control surface for how the world behaves: who can join, how hard combat feels, how far chunks load, and what friends see in the multiplayer list. It is not a plugin. It is not Paper config. Change it carefully, with a named backup first.

This guide is for friend SMPs and small communities on GlassHosting. Glass Gaming, powered by GlassHosting. New to the panel? Read the game panel beginner guide. For the safe edit habit, use Stop, Backup, Edit, Start.

1. Quiet window, Stop, named Backup

Tell the group the server is going down for a config edit.
Open the service in panel.glasshosting.com.
Click Stop and wait for a clean stopped state.
Take a named backup labeled for this change (example: pre-server-properties-2026-10-01).

Do not edit server.properties while the process is running. Live writes and a mid-boot rewrite are how you get half-applied settings and confused friends.

2. Open the file (File Manager or SFTP)

With the server Stopped:

File Manager for a quick line change (short files, one property).
SFTP if you prefer a local editor, or you are stacking several changes.

The file lives in the service root next to the world folder, usually named exactly server.properties. Full File Manager vs SFTP detail: Panel File Manager and SFTP.

3. Essentials home users actually change

Leave unknown keys alone. Change only what you understand. Values are case-sensitive for enums like gamemode names on many builds. Prefer the spelling your current Paper or Vanilla build already uses in the file.

Property	What it does	Typical private SMP note
`gamemode`	Default mode for new joins (survival, creative, adventure, spectator).	Friend SMPs usually stay on survival. Pair with `force-gamemode` if people keep switching.
`difficulty`	peaceful / easy / normal / hard.	Normal is the common friend default. Hard is fine if everyone agrees.
`max-players`	Hard join cap the server advertises and enforces.	Set to the real community size, not a fantasy slot count. Honest slots beat idle ghosts.
`motd`	Message of the day in the multiplayer list.	Keep it short. Color codes are optional polish. See also server icon and MOTD.
`white-list` / `enforce-whitelist`	Only approved names can join when enabled.	Private realms should enable whitelist. Walkthrough: whitelist players.
`online-mode`	Validates against Microsoft / Mojang accounts when true.	Keep `true` for public-facing Java unless you have a deliberate offline design and understand the risks.
`view-distance`	How far clients see chunks.	Higher looks prettier and costs more CPU/RAM. Drop it before you blame “the host” for TPS.
`simulation-distance`	How far the server simulates entities and redstone (modern Java).	Often the bigger performance lever than view-distance. Lower it before buying more RAM you do not need. See RAM sizing and TPS triage.
`spawn-protection`	Blocks non-ops from building near world spawn (block radius).	Set `0` if ops build the spawn hub and friends need to place blocks there.
`pvp`	Player vs player combat on/off.	Private friend servers often leave this true and use social rules, or set false for pure co-op.
`allow-nether`	Nether dimension enabled.	Usually true. Turn off only for a deliberate challenge map.
`enable-command-block`	Command blocks execute when true.	Leave false until you need them. They are powerful and easy to break a world with.
`level-name`	Folder name for the world the server loads.	Must match the world folder on disk. Wrong name = “empty” new world. Related: upload a world.
`level-seed`	Seed used when generating a brand-new world.	Changing seed on an existing world does nothing useful. New world only.
`hardcore`	Hardcore rules when true.	Do not flip this on a lived-in survival world as a joke. Take a named backup first if you ever experiment.

Paper vs Spigot vs Vanilla still matter for plugins and performance: Paper vs Spigot vs Vanilla.

4. Save, Start once, smoke-test

Save the file. Confirm there are no stray smart quotes or half-deleted lines.
Click Start once. Watch the console.
Have one trusted friend join with the panel IP and port (how friends join).
Verify the change: gamemode, difficulty, MOTD, whitelist behavior, player cap.

If the server will not boot, or settings look wrong, Stop and restore the named backup. Do not keep stacking edits on a broken file.

Common mistakes

Editing while the server is still Online.
Changing level-name without uploading or renaming the matching world folder.
Cranking view-distance and simulation-distance then filing a lag ticket.
Disabling online-mode “to fix joins” when the real problem is IP:port or whitelist.
Skipping the named backup. Restore exists for this exact class of mistake.

When to ticket

Console errors after a properties edit you cannot decode.
Whitelist or online-mode behavior that still blocks friends after a correct restart.
You need help matching Paper build behavior to a property that changed across versions.

Ticket from billing.glasshosting.com. Paste the property you changed, the named backup label, and the console lines. Skim the billing knowledgebase for Minecraft how-tos already published.

Quick checklist

Players out; quiet window agreed
Server Stopped; named Backup taken
Only known properties edited; file saved cleanly
Start once → console clean → one-friend smoke-test
Restore named backup if boot or behavior is wrong

Related guides

MSP note

GlassHosting treats config edits like store changes: stop, labeled backup, edit, start, smoke-test. Order or manage plans at billing.glasshosting.com; operate day-to-day at panel.glasshosting.com. Glass Gaming, powered by GlassHosting.