Skip to content
Minecraft advanced · 13 min read

Minecraft Server Config Editor: Edit server.properties in LoafHub

Use the LPV5 Minecraft config editor to edit server.properties in-browser, plus whitelist, ops and YAML files. No FTP, no SSH.

By Bradford Updated

The fastest way to edit server.properties on a Loafhosts Java server is the Config Editor built into the LPV5 panel. It gives you a friendly form for every common setting, from difficulty and gamemode to MOTD and view distance, while still letting you open the raw files when you want full control. You never touch FTP or SSH, and the JSON files (whitelist, ops, bans) are syntax-validated before they save, so a stray comma can’t reach the server. YAML edits are not validated, so the editor warns you and a bad indent can still break boot. This guide walks through both the form editor and the raw editors, explains which files the tool exposes on each loader, and covers the one gotcha that trips everyone up: most changes only apply after a restart.

What the Config Editor Does

The Config Editor is the in-browser file editor for your server’s configuration. Instead of downloading server.properties, editing it locally, and uploading it back, you open it in the panel and change values directly. The tool is split into two halves: a structured form editor for server.properties, and raw editors for the JSON and YAML files that the form cannot represent cleanly. The file list adapts to your loader, so a Paper server shows Paper, Spigot and Bukkit YAML files while a Purpur server adds purpur.yml on top.

Note: Loafhosts runs Java Edition servers, and Purpur is the default server type (a Paper fork), so the form editor and the Paper and Purpur YAML files are available out of the box

Note: Everything is edited in your browser inside LoafHub, so no FTP client or SSH access is required

Open the Config Editor

Every tool in the panel lives behind the same starting point: log in to LoafHub, open your server, and pick the tool you need. The Config Editor is reached the same way.

  1. Sign in to LoafHub at hub.loafhosts.com
  2. Open your Minecraft server from your server list
  3. Open the Server Config tab (the Config Editor is labelled Server Config in the sidebar)
  4. Pick the file you want to edit from the file list
  5. Make your changes, then save

Tip: The file list reflects your loader, so if you switched loaders recently you may see new files like purpur.yml appear

Tip: Bookmark hub.loafhosts.com so you can jump straight to your server when you need a quick edit

Edit server.properties with the Form Editor

The form editor is the friendly way to edit server.properties. Each setting is a labelled field, so you change difficulty with a dropdown and max-players with a number box rather than hunting through a flat text file. Crucially, the editor preserves the comments and the original ordering in the file when it writes your changes back, so the file stays readable and diff-friendly. The example below shows the kind of keys you will be editing.

CommandDescriptionExample
difficultyWorld difficulty for the whole serverdifficulty=normal
gamemodeDefault gamemode new players join ingamemode=survival
max-playersMaximum simultaneous playersmax-players=20
motdThe message shown under the server name in the multiplayer listmotd=Welcome to the Loaf SMP
pvpWhether players can damage each otherpvp=true
view-distanceChunks the server sends around each playerview-distance=10

Tip: Loafhosts servers have unlimited slots, so max-players is a soft cap you choose for gameplay, not a plan limit

Tip: Lowering view-distance is one of the simplest ways to reduce server load on a busy world

Raw Editors for JSON and YAML Files

Some files are lists or deeply nested structures that a form cannot represent well, so the tool gives them raw editors instead. The JSON access-control files, whitelist.json, ops.json, banned-players.json and banned-ips.json, open in a JSON-validated editor that warns you before you save invalid syntax. The same raw editing is available for the Paper, Spigot and Purpur YAML files so you can tune the deeper server behaviour by hand.

Warning: YAML is whitespace-sensitive, so keep the existing indentation when you edit Paper or Spigot files by hand

Note: The JSON editors validate your syntax, so a stray comma or missing bracket is caught before it ever reaches the server

Note: For day-to-day moderation, the Player Manager edits these same JSON files for you with live console actions

Networking Keys You Should Leave Alone

A few keys in server.properties control how your server is reachable on the network, and Loafhosts manages those for you. The networking keys, server-port and query.port, along with the RCON settings, are editable in the Config Editor, but you should not change them. Only your allocated port is forwarded, so editing server-port makes the server unreachable, and the platform already has these set correctly for you.

Note: Loafhosts assigns and manages your port. The field is editable, but do not change server-port, only your allocated port is forwarded, so changing it takes the server offline

Note: Panel tools like the Player Manager run console commands by sending them straight to the server console via LoafWings, so they work without any RCON setup

Apply Your Changes with a Restart

This is the gotcha that catches almost everyone. A Minecraft server reads server.properties and its other config files when it boots, so your saved changes do not take effect while the server is running. After you save, restart the server so it re-reads the files. Until then, the live server keeps using the old values even though the editor shows the new ones.

  1. Save your changes in the Config Editor
  2. Open the Console tab
  3. Restart the server
  4. Wait for the server to finish loading
  5. Reconnect and confirm the new settings are live

Warning: Do not use the Config Editor to accept the EULA, the eula.txt file is handled by the separate EULA Helper, which writes eula=true for you

Common server.properties Edits and What They Do

Most people open the Config Editor to change the same handful of settings. Here is a quick reference for the ones you will reach for most, all of which live in the server.properties form.

Tip: Set difficulty to hard for a survival challenge, or peaceful to disable hostile mobs entirely

Tip: Change gamemode to creative for a build server, then keep PVP off to avoid griefing

Tip: Edit the MOTD seasonally to advertise events without renaming the whole server

Tip: Tune view-distance and simulation-distance together to balance render range against performance

Frequently Asked Questions

How do I edit server.properties on a Loafhosts server?

Open the Config Editor in the LPV5 panel inside LoafHub, select server.properties, and change the values in the form editor. Save your changes, then restart the server so they take effect.

Do I need FTP to use the config editor?

No. The Config Editor runs entirely in your browser inside LoafHub. You open and save files directly in the panel, so no FTP client or SSH access is needed.

Why didn’t my server.properties change take effect?

Minecraft only reads server.properties when it starts up. After you save in the Config Editor, you must restart the server from the Console tab for the new values to go live.

Which config files can I edit besides server.properties?

You get JSON-validated raw editors for whitelist.json, ops.json, banned-players.json and banned-ips.json, plus raw editors for the Paper, Spigot and Purpur YAML files. The file list adapts to your loader.

Should I change the server port or RCON settings?

No. These are host-managed networking keys. Loafhosts sets server-port, query.port and RCON for you. They are editable in the Config Editor, but only your allocated port is forwarded, so changing server-port will take your server offline. Leave them alone.

Does editing the config keep my comments intact?

Yes. The form editor for server.properties preserves the file’s comments and original ordering when it writes your changes back, so the file stays readable.

Rate this guide

Tap a star — it helps us decide what to write (and fix) next.