Common config fields

Safe editing checklist

• Stop the server before editing the config file.
• Make a copy of the last working config.json.
• Keep JSON punctuation valid: quotes, commas, braces, and true/false values matter.
• Change one value, restart, and test before changing more.
• If friends cannot connect after changing the port, update firewall and router rules to match.

Example config

{
  "AutoStartWorldName": "auto",
  "AutoCreateAndLoadWorld": true,
  "AutoCreateWorldSize": 1,
  "Password": "change-me",
  "Port": 8050,
  "MaxPlayers": 8,
  "EnableCheats": false
}

Setup checklist

1. Install the standard .NET 8 Runtime. On Windows, confirm it with dotnet --list-runtimes; on Linux, install the .NET 8 runtime package or Microsoft install script.
2. Install SteamCMD, then download the Romestead Dedicated Server using anonymous login and App ID 4763510.
3. Choose whether to self-host on your PC, a spare machine, a VPS, or a managed game host.
4. Start the server once so it can create its current world and config files.
5. Back up the original config.json or equivalent generated config before editing.
6. Open UDP port 8050 in the host firewall, and forward UDP 8050 on your router if friends connect from outside your network.
7. On Windows, start the server executable from the server folder. On Linux, run the server DLL with dotnet if the build uses Server.dll.
8. Test direct connection with one player, then set up a basic save backup routine.

Minimum planning notes

Basic SteamCMD flow

1. Create a clean folder for the server, such as C:\romestead-server or /home/steam/romestead-server.
2. Start SteamCMD.
3. Set your install directory before downloading so files do not land in the wrong place.
4. Run the Romestead Dedicated Server update with App ID 4763510.
5. After download, install .NET 8 Runtime if the server does not start.
6. Launch the server once before editing config files.

Example commands

force_install_dir C:\romestead-server
login anonymous
app_update 4763510 validate
quit

On Linux, use a Linux path after force_install_dir. Keep the folder simple and avoid spaces while you are still testing.

Common install mistakes

What to do after download

Do not jump straight to router settings. First make sure the server starts locally, creates its config, and keeps running. After that, back up the config, set the server name and password, then open UDP 8050 for outside players.

Quick Windows check

1. Open PowerShell in the server folder instead of double-clicking the executable.
2. Run dotnet --list-runtimes.
3. Look for a line starting with Microsoft.NETCore.App 8..
4. If it is missing, install the .NET 8 Runtime from Microsoft, then restart the PC if the server still cannot see it.
5. Launch the server again from PowerShell so any error message remains on screen.

What the symptoms usually mean

Runtime vs SDK

Most players only need the .NET 8 Runtime to run a dedicated server. The SDK is mainly for developers. If you are trying to keep setup simple for a friend group, install the runtime first and only add the SDK if official server notes specifically ask for it.

After the runtime is fixed

Once the server stays open, do not edit everything at once. First confirm it creates a world, then back up the generated config, then open UDP 8050, and only then invite friends to test direct connection.

Fast diagnosis

UDP 8050 checklist

1. Confirm the server config uses port 8050, or note the custom port you changed it to.
2. Allow the Romestead server executable through Windows Defender Firewall.
3. If using Linux, allow UDP 8050 in your firewall tool, such as ufw or provider firewall rules.
4. On your router, forward UDP 8050 to the hosting PC's local IP address.
5. Make sure the host PC keeps the same local IP. DHCP changes can break forwarding.
6. Ask a friend to test direct connect using your public IP and port.
7. If direct connect works but the browser does not, keep using direct connect while the listing catches up.

Common mistake: TCP only

Many router screens ask whether a rule is TCP, UDP, or both. If you only create a TCP rule, friends may still fail to connect. For Romestead server hosting, make sure UDP 8050 is allowed. Choosing both TCP and UDP is usually fine if your router interface is unclear.

When to stop debugging

If your home router, ISP, or shared apartment network blocks inbound connections, managed hosting may be faster than fighting network rules. That is the strongest monetization angle for this site later: the user already has a concrete reason to pay for hosting.

Fast checklist

1. Confirm the server console is still running and not stuck during world generation.
2. Ask one friend to try direct connect with your public IP and port 8050.
3. If direct connect works, the server is reachable; the browser may simply be delayed or filtered.
4. If direct connect fails, return to UDP 8050 firewall and port forwarding checks.
5. Restart the server after changing the config name, password, or port.
6. Use a clear server name so friends can search for the exact text.

What to try before rebuilding

Do not confuse visibility with reachability

A public server list can lag, filter, or temporarily fail to show a working server. Direct connect is the better first test because it tells you whether the server is reachable at all. If direct connect works, keep playing and solve visibility later.

Hosting angle

Players who cannot get a stable listing often care about uptime, fixed IP behavior, restarts, and fewer network rules. That makes this page a natural bridge to a future hosting comparison page without making the article feel like an ad.

When to make a backup

• Before running a SteamCMD update.
• Before editing config.json or changing world startup settings.
• Before moving from a home PC to a VPS or managed host.
• Before testing large world generation or changing player limits.
• After a long session where the group made major progress.

Simple backup routine

1. Tell players the server is going down for a quick backup.
2. Stop the server cleanly and wait for the process to exit.
3. Copy the world/save folder, config file, and any server settings into a dated folder.
4. Name the folder clearly, for example 2026-05-31-before-update.
5. Keep at least three recent backups instead of overwriting the same one.
6. Restart the server and confirm the current world still loads.

Backup schedule

Restore test

A backup is only useful if you know how to restore it. Test with a copy: stop the server, replace the world files with the backup copy, start the server, and confirm the world appears. If the restore process is confusing, document the exact folder names before your group depends on it.

Hosting angle

Backups are one of the cleanest monetization bridges for this site. Players do not pay because they love hosting panels; they pay because they want the world to stay online and recoverable when something breaks.

Quick recommendation

Hosting scorecard

Recommended host checklist

• Can you upload and download save backups?
• Can you restart the server from a browser panel?
• Can you edit config files without using SSH?
• Does the host expose the Romestead server port clearly?
• Can you choose a location near your player group?
• Does support understand SteamCMD dedicated servers?
• Can you cancel monthly without long commitments?

Future recommendation slots

This page intentionally has no paid link yet. The goal is to build trust first, then add a small number of tested recommendations when there is enough traffic to justify it.

When not to pay yet

• You have not confirmed that your friends enjoy the game long enough to need 24/7 uptime.
• You only need a one-night test server.
• You have not learned where saves and config files are stored.
• You cannot download your own backups from the provider.

Sources checked

Setup details were cross-checked against the Romestead Wiki dedicated server guide, SteamDB App ID 4763510, and current hosting provider setup pages. Hosting recommendations should be tested before adding affiliate links.