uniz.host
MinecraftI changed a Minecraft server setting and nothing happened
Last updated September 30, 2026
Nothing is broken — the save worked. A Minecraft server reads server.properties when it boots, and your server's pod is deliberately never recreated behind your back, so every server field on the Settings tab (MOTD, difficulty, game mode, seed, view and simulation distance, max players, spawn protection, online mode, whitelist, JVM flags, the server icon) is stored the instant you save and applied on the next restart. The amber "Changes pending a restart" banner is the signal that a save is waiting. Gamerules are the one exception: they go over RCON and take effect immediately, no restart.
- Open the Settings tab and the group that holds the field
- Change the field you came for
- Save, and watch for the pending-restart banner
- Restart the server to apply it
- Confirm the change actually landed
On this page · 7 sections
You opened the Settings tab, changed the difficulty, hit save, saw a confirmation — and in game the mobs are still exactly as friendly as they were. Nothing failed. This page is about what the save actually did, why the running server did not care, and what each field on the Settings tab is really for.
Why the change did not take: a running server never re-reads its settings
A Minecraft server reads server.properties once, when it starts. Everything after that runs from memory. That is Minecraft's own behaviour, not something the hosting adds.
What uniz.host adds on top is a deliberate promise: your server's container is never recreated behind your back. When you save, the new configuration is written to your server's record and pushed onto the pod template right away — but the platform explicitly tells Kubernetes not to roll the running pod for it. The consequence is exactly the one you noticed: the setting is saved, and the world you are standing in still has the old value.
The settings page says so plainly: every section that holds server.properties values carries an "Applies after a restart" tag, and if the server was running when you saved, an amber "Changes pending a restart" banner appears at the top of the server page, saying the changed settings take effect after the next restart, with a "Restart now" button. That banner is the whole signal. It is not a warning that something went wrong; it is a receipt.
Two edge cases worth knowing. If the server was stopped when you saved, no banner appears at all — there is nothing to be out of date, and the change is already in place for the next start. And if your server is crash-looping, there is no Restart button to press (it only works on a server that is actually running); stop it and start it again instead, which applies the pending changes the same way.
The one exception: gamerules are instant
Every section tagged Applies after a restart waits for one. Gamerules do not. keepInventory, doDaylightCycle, mobGriefing and the rest are sent straight into the live server over RCON, so their section is tagged Applies at once instead, which is why those switches only work while the server is running, and why those values are not stored in our database at all — they live inside the world file. They have their own page: Minecraft gamerules.
The other live-applying group is the sleep block — the auto-sleep window, the asleep MOTD, the wake message and the wake allowlist. Those are configured on the router that sits in front of your server rather than inside the server, so they update without touching the running world.
How to change a setting so it actually takes effect
Open the Settings tab and the group that holds the field
Go to /dashboard/servers, open the server, and pick the "Settings" tab. A Minecraft server's values are split across its groups:
| Group | Fields in it |
|---|---|
| General | Name, server icon, MOTD, asleep message and time zone |
| Connection | Online mode (under the crossplay section, where the server can have crossplay) |
| Game rules | The Gameplay, Players and World sections, then the gamerules |
| Version and performance | Java runtime, JVM performance flags and the Performance section (simulation distance, view distance) |
If you are not sure which group holds a field, type its name into "Search settings" at the top. You need to be the owner, or a team member the owner granted the settings permission — without it the fields render read-only.
Change the field you came for
Under each field's label its real server.properties name is printed small, such as difficulty or view-distance, so you can match it against guides written elsewhere. A field whose value differs from the default gets an orange bar on its left, a bold label and a "Reset to default" button, and the "Changed from default" button at the top of the Settings tab lists every field you have changed in one place.
Save, and watch for the pending-restart banner
As soon as you change a field, a save bar appears at the bottom of the group with the count of changed values. Hit "Save". You should get a "Saved" toast, and — if the server is running — the pending-restart banner at the top of the page. Only the fields you actually touched are sent; everything else keeps whatever it had. While the server is running the save bar also offers "Save and restart", which saves and restarts in one go; if you used it, skip the next step. Each group has its own save bar, so changes in two groups need two saves.
Restart the server to apply it
Press "Restart now" on the pending-restart banner, or "Restart" in the server's header. Players online are disconnected briefly and the world is saved before shutdown. The banner clears once the server comes back on the new configuration.
Confirm the change actually landed
Do not trust the form; check the result. Difficulty, game mode and PvP are visible in game within seconds of joining. The MOTD, the icon, max players and the hidden-players setting show on the multiplayer list without joining. If the change is not there after a restart, the console tab is the place to look — a server that failed to boot never applied anything.
What each field really changes
MOTD (the "Server-list message while on (MOTD)" field in General) is the message under your server's name in the multiplayer list, and it is two independent lines of up to 60 characters each. § colour and style codes work in it. Leave it blank and the server image writes its own default line. On Bedrock the field is "MOTD (server list name)", there is one line only, and it replaces the server name in the list rather than sitting under it.
Difficulty and game mode are the two most-changed fields on the Settings tab. Game mode sets what new players join as — it does not retroactively convert players who have already been on the server, unless you also switch on force gamemode on join in the Players section.
World seed and world type are the fields that surprise people most: they affect newly generated chunks only. The terrain already on disk was generated with the old values and is not touched, so changing them alters what you find when you walk into unexplored land, not the base you already built. Both are Java-only.
View distance and simulation distance are separate knobs that people routinely confuse. View distance is how far the world is sent to the client — it is what players see. Simulation distance is how far from a player the world stays active: mobs move, crops grow, redstone runs. Lowering simulation distance is the cheaper of the two for performance, because it reduces work rather than just what is drawn. Both accept 3–32 on Java. On Bedrock, simulation distance is called tick distance and only accepts 4–12, so we clamp your value into that range before it reaches the server.
Max players (1–200) is a cap on concurrent connections and nothing else — raising it does not give your plan more RAM, and a number your plan cannot feed just turns "server full" into lag. Pick it against the RAM you actually bought; Game server RAM has the numbers.
Spawn protection is the radius in blocks around world spawn where non-operators cannot build or break. 0 to 64, and see the defaults section below before comparing it against a guide from elsewhere.
Online mode verifies every joining player against their Mojang/Microsoft account. It sits in the Connection group. Turning it off is the single riskiest control on the Settings tab, and a "Security risk" box appears under it the moment you do: the server stops checking accounts entirely, so anyone can join under any username — including your own, or an operator's. Anyone who can reach the address can then claim operator identity. If you have a reason to turn it off, the whitelist stops being optional.
Whitelist is a switch, not a list. Turning it on means only players you have added can join; it does not add anyone. The names themselves live in the Players tab, which reads and writes the server's whitelist file — and works whether the server is running or stopped. A whitelist switched on with an empty list locks everyone out, including you.
JVM performance flags (the Java section of Version and performance) is one select with three choices: "None", "Aikar's flags", the long-standing garbage-collection tuning most servers run, and "MeowIce's flags", a newer set tuned for Java 17 and up. You can pick only one, so there is no way to end up with both. Both are ready-made presets; you never hand-write JVM arguments here. Which Java version the server boots on is a separate field, covered in Java runtime for Minecraft.
The server icon is stored as soon as the square crop uploads, and you get "Icon uploaded". Restart the server to replace the icon file in the world. Removing the icon takes effect when you save the General group; the last icon your world received remains until a new one replaces it. Java only; the Bedrock server has no server-icon file.
Two defaults here that differ from vanilla
If you compare the settings page against a Minecraft guide written for a hand-built server, two values will not match, and both are on purpose:
| Setting | On a server created here | Vanilla |
|---|---|---|
| Spawn protection | 0 — nothing around spawn is locked | 16 blocks |
| Hide online players | on — names and count hidden on the list ping | off |
These are seeded when the server is created, so a Java server made on uniz.host starts with them. Older servers whose owner never saved these values keep whatever they had; to get our defaults, press "Reset to default" on the row and save.
What Reset to default does
Every field whose value differs from the default has a "Reset to default" button on its row. Pressing it puts the field back to our default — the value a new server gets, so spawn protection goes back to 0, not 16. It does not save anything by itself; it only changes the value in the field, and you still press "Save" on the group's save bar. Like every field in these sections, the restored value applies after a restart.
Read next
- Minecraft gamerules — the settings that do apply instantly
- Java runtime for Minecraft — which JVM your server boots on, and how Auto picks it
- Game server RAM — what max players and view distance actually cost you
- Dashboard tour — reading the rest of the server page
Frequently asked questions
I saved a setting and nothing changed in game. Did the save fail?
No — the save succeeded and is stored. A Minecraft server reads server.properties once, at boot, and your server's pod is deliberately never recreated behind your back, so the running world keeps the old value until the pod is replaced. Restart the server and the new value is there. If the server was running when you saved, the amber "Changes pending a restart" banner appears to say exactly that; if it was stopped, there is no banner and the change simply applies on the next start.
Which Minecraft settings apply without a restart?
In the sections tagged Applies after a restart, none of them — every field is written into the pod's configuration and read at boot. The exception is the gamerules section at the end of the Game rules group: rules such as keepInventory or doDaylightCycle are pushed over RCON to the live server and take effect immediately, which is why those switches only work while the server is running. Sleep settings, the asleep MOTD and the wake message are also applied live, because those live on the router in front of your server rather than inside it.
I changed the world seed and my world looks exactly the same.
That is the correct behaviour. The seed and the world type only steer how brand-new chunks are generated — terrain that already exists on disk was generated with the old values and never regenerates. Walk far enough into unexplored land after a restart and you will see the new settings take over, usually with a visible seam where the two generations meet. To get a whole world on a new seed you have to reset the world, which is a separate, deliberately destructive action with its own confirmation.
Why is my spawn protection 0 when every Minecraft guide says the default is 16?
Because a Minecraft server created on uniz.host is seeded with spawn protection 0 rather than the vanilla 16, so nothing near spawn is locked for ordinary players out of the box. It is a deliberate platform default, not a bug, and you can set anything from 0 to 64 in the Gameplay section of the Game rules group. The other default that differs the same way is hide online players, which is on here and off in vanilla.
Is it safe to turn online mode off so friends without accounts can join?
It removes the only thing stopping impersonation. With online mode off, the server stops checking accounts entirely — anyone who can reach the address can join under any username, including the exact username of one of your operators, and walk in with full permissions. If you turn it off, treat the whitelist as mandatory rather than optional, keep the operator list tiny, and expect that a username is no longer proof of identity.
Why does my Bedrock server show so few settings?
Because the Bedrock dedicated server has no equivalent for most of them. Only motd, difficulty, game mode, max players, view distance, simulation distance, online mode and whitelist have a Bedrock counterpart, so those are the only ones rendered — and the API rejects the rest instead of accepting a setting it would silently drop. Two of the eight are renames rather than the same key: the MOTD becomes the single-line name shown in the Bedrock server list, and simulation distance becomes tick distance with a narrower 4–12 range.
Related guides
Would you rather skip all of this?
A server on uniz.host is up in minutes. You pay by the hour only while it is online, and the smallest top-up is ฿20.