Can't Join a Smalland Server After an Update (Fixes)
Smalland server visible but joining fails after a patch? Match game versions, back up and update the server, check World Name, password and a full server.
Updated Oct 7, 2026 · 5 min read
On this page
- Why updates break joining
- Step 1: Back up the world first
- Step 2: Update the server
- Step 3: Update every player
- Step 4: Check Cross Play and the browser
- Step 5: Make sure it loaded your world
- Other reasons joining fails
- Settings that look broken after an update
- Preventing the next one
- Patch days without the scramble
- FAQ
When a Smalland server shows in the browser but joining fails right after a game update, the server is almost always still on the old build while players have the new one. Back up the world, update the server, restart it, and have every player restart Steam so they are on the same version. If joining still fails, check that World Name still points at your save (a mismatch silently starts a fresh world), that the password is right, and that the server is not at its 10 player cap.
Why updates break joining
Smalland's players update automatically through Steam. A dedicated server only updates when it is told to: a self hosted server when you run SteamCMD, a hosted one when it restarts with auto update on. Between the patch and your server update, players are on build N+1 and the server is on build N, and Smalland will not let them play together. Depending on timing you might see the server in the list and fail to join, or not see it at all.
Step 1: Back up the world first
Bigger Smalland patches can change save data, and an update is the moment a world is most at risk. Before you update the server:
- Stop the server.
- Copy the world save folder somewhere safe, or take a backup from your control panel.
If the updated server will not load the old world, you can roll back to the backup and wait for a fix rather than lose weeks of building. Our backup guide covers good habits.

Step 2: Update the server
For a self hosted server:
steamcmd +force_install_dir /home/smalland/server +login anonymous +app_update 808040 validate +quit
validate also repairs files an interrupted update may have left broken. Start the server and watch the console until the world has loaded and the server is online.
Step 3: Update every player
Ask everyone to fully restart Steam so the patch installs, then launch Smalland. Anyone who had the game open during the update may still be on the old version. If someone opted into a beta branch (right click Smalland in Steam, Properties, Betas), they need to be on the same branch as the server.
Step 4: Check Cross Play and the browser
After an update, game settings occasionally reset. Players need Cross Play on to see dedicated servers. Then Join, filter Public, and search the exact server name. If the server does not show at all, see Smalland server not showing in the server browser.
Step 5: Make sure it loaded your world
A common scare after an update: friends get in, but the world is brand new. The server loads the save named in its World Name setting. If that name changed, was mistyped, or the save files were moved, the server quietly creates a new world under that name.
- Check World Name matches your save exactly.
- Check the save files are where the server expects them.
- If you uploaded a world from someone's PC before, our guide to moving a Smalland world shows where the files go.
Do not let players build on the accidental new world. Stop the server, fix the name, and start again, so the real save is not overwritten by confusion later.
Other reasons joining fails
| Symptom | Cause | Fix |
|---|---|---|
| Password rejected | Password changed or mistyped | Check the server's password setting; restart after changes |
| Server full | 10 player cap reached | Smalland supports up to 10; wait or rotate players |
| Join times out | Game port blocked on a self hosted server | Forward the UDP game port and allow it in the firewall |
| Kicked straight back to menu | Server still loading the world | Wait until the console shows it is online |
| Works for everyone but one | That player's version or Cross Play | Restart Steam, check Cross Play, verify files |
Settings that look broken after an update
Smalland servers read their settings at start. If a patch changed defaults and your server feels different, confirm the modifiers you rely on (creature health and damage, hunger, day and season length, friendly fire, peaceful mode, keep inventory) are still what you set, then restart.
Preventing the next one
- Keep auto update on for your server, and restart it when you see a Smalland patch announced.
- Take a backup before every restart that will update the game.
- Tell your group to restart Steam after patch announcements.

Patch days without the scramble
On a GamezServers Smalland server, Auto Update is a panel setting, so a restart from the panel brings the server to the newest build. One click backups make the before update snapshot painless, and World Name, Password and every gameplay modifier are panel fields, so a reset setting is easy to spot. The live console shows when the world has loaded. If you are not running a server yet, how to host a Smalland server covers the basics.
FAQ
Why can't I join my Smalland server after a patch?
The server is on the previous build. Update it, restart it, and make sure every player restarted Steam to get the patch.
Will a Smalland update delete my world?
Normally not, but bigger patches can change save data. Back up before updating so you can roll back if the world fails to load.
Why is my Smalland world empty after an update?
The server is loading a different save than before, usually because World Name changed or the files moved. Fix the name and restart.
How many players can join a Smalland server?
Up to 10. A full server turns away the eleventh player.
Skip the setup. Your own Smalland: Survive the Wilds server.
Then $14.99/mo. Just trying it? $3.75 for 3 days