Fix common Romestead server errors

Most Romestead server problems are a version mismatch, the wrong port, or a world name that doesn’t match. Start at the top and work down.

Joining problems

Client version 0.X.X_X is not compatible with server version 0.X.X_Y

The numbers in the message change with each version.

Why: Your game and the server are on different Romestead versions. The developers say the side with the lower number needs to update.

Fix:

1. If your game has the lower number, update it in Steam. If no update shows, restart Steam.
2. If the server has the lower number, restart it from Overview. It installs the newest version on start, unless you pinned one in Settings.
3. If you switched to a beta branch in Steam, switch back to the normal version. A beta game can’t join a server on the normal version.

The connection times out

Why: The port is wrong, or the server is still starting or waking.

Fix:

1. Check you used the port from the address card on Overview, not 8050.
2. Check the status on Overview. Wait until it says Running, then join again.
3. After a long nap, waking can take longer than the game waits. Connect a second time, or open the wake link (play.wilderack.com/w/forum) first.

The game won’t take the address

Why: Some versions of the join screen only take an IP address, a number like 203.0.113.25.

Fix:

1. On Windows, open Command Prompt.
2. Type nslookup forum.play.wilderack.com, using your server’s address, and press Enter.
3. Use the number shown under “Address” in the address box, and the port from the address card in the port box.

The password doesn’t work

Why: It was changed, it’s typed in the wrong case, or the server hasn’t restarted since it was changed.

Fix: check the password in Settings, restart the server so the new one applies, and type it again. Passwords are case-sensitive.

Players keep getting disconnected

Why: The developers say most disconnects happen when network messages between a player and the host arrive too late. Often it’s the player’s connection.

Fix:

1. Check whether it’s one player or everyone. If it’s one player, have them try a wired connection or turn off their VPN.
2. If everyone gets disconnected, check the CPU and RAM graphs on Overview. A server at its limit can’t keep up.
3. Keep the server and every player on the same, newest version. The developers keep working on fewer disconnects in each update.

World and save problems

The server made a new world instead of loading mine

Why: AutoStartWorldName in config.json doesn’t match any world folder in saved_worlds. Because AutoCreateAndLoadWorld is on, the server made a fresh world with that name.

Fix:

1. Stop the server.
2. In Files, open saved_worlds and note your world’s folder name.
3. Set AutoStartWorldName to exactly that name. Capitals count.
4. Start the server.

Your new, empty world stays in its own folder and does no harm. Delete it later if you like.

The newest save won’t load

Why: The last save was cut short, for example by a crash.

Fix:

1. Restart the server. Romestead keeps one rolling backup of each world and tries it by itself when the newest save fails.
2. If that doesn’t work, restore a backup from Backups. We make a safety backup of the current state first.

Making a large world fails

Why: Not enough memory. Making a large world needs 8 GB of RAM.

Fix: move up to an 8 GB plan, or set AutoCreateWorldSize to 1 for a standard world. See performance.

Server problems

The server won’t start after editing config.json

Why: A typo in the JSON, like a missing comma or quote, or a setting name with the wrong capitals.

Fix:

1. Open the Console. The last lines usually point at the problem.
2. Open config.json under Settings > Advanced, which checks the JSON before saving, and fix the line.
3. Or restore config.json from a backup, through Files.

The server crashes when people play

Why: Usually not enough memory for your group or world size.

Fix:

1. Look at the crash helper card in the Console and follow its hint.
2. Check the RAM graph. If it hit your plan’s limit, move up a plan: 4 GB for a standard world and up to 4 players, 8 GB for more.
3. If RAM was fine, send us the console lines from the crash card.

Cheats don’t work on the server

Why: EnableCheats is off, or it was turned on after the world was made. The community wiki says it only works if it’s on when a world is first made.

Fix: to play with cheats, make a new world with EnableCheats set to true from the start.

Still stuck?

Write to us at support@wilderack.com with your server’s name and what you see. Real people read every message. For bugs in the game itself, the developers read reports on Steam and their Discord.