Log in
‹ Back

SERVER SETUP

New here? Open The Basics first. Already know your game? Pick it below.

What a dedicated server is

A game server is a computer that keeps a game world running so other people can join it over the internet.

A dedicated server is a copy of the game made only for that job. It has no screen and no player in it. It just runs the world and lets people in.

Why not host from inside the game? Some games let you do that, but the world closes when you quit. A dedicated server stays up, so your friends can play when you are not.

That is all it is: a program on a computer that stays on.

Self-host or paid host

You have two choices for where the server runs.

Self-host means it runs on a computer at your home.

  • You do not pay a host each month. You do pay for power, and the computer has to be on whenever friends want to play.
  • You set up your own router (the next section explains how).
  • Your friends connect to your home internet address, so only share it with people you trust.
  • Your home internet speed and any limits from your ISP (internet service provider, the company you pay for internet) apply.

Things that can get in the way at home. You do not need to understand these yet. If something stops working, open the list.

Double NAT, CGNAT, DHCP and ISP limits explained
  • Double NAT (double network address translation). NAT is how a router shares one internet connection between all your devices. If two routers are chained (for example, your ISP's box plus your own router), each one does this, and the doors you open on one are still shut on the other.
  • CGNAT (carrier-grade NAT). Some ISPs share one public address between many homes. Then your home has no public address of its own to open doors on.
  • DHCP (Dynamic Host Configuration Protocol). This is the router feature that hands out addresses to the devices in your home. It can give your server computer a new address after a restart, and then your door rule points at the wrong place. Step 3 of the next section fixes this.
  • ISP limits (internet service provider limits). Some ISPs block certain doors (ports) or limit what you can open.

How to check for each of these is in the box at the bottom of Ports and port forwarding.

Paid host means you rent a server from a company.

  • It is on all the time and there is no router to set up.
  • Most hosts have a panel where you click to start, stop and change settings.
  • You pay every month, and you are limited to what your plan allows.

Not sure which? If you do not want to touch your router, rent one. If you have a spare computer and like to tinker, self-host. Neither choice is wrong, and you can switch later.

Compare hosts and prices

Ports and port forwarding

Think of your home internet address as a building's street address. A port is a numbered door on that building. A game server listens at certain door numbers, and each game uses its own (the game tabs list them).

Your router is the front desk. By default it does not let strangers in. Port forwarding is telling the router: "When someone knocks on door number X, send them to the server computer."

You only need this if you are self-hosting. A paid host does it for you.

Words you will see
  • IP address (Internet Protocol address): the number address of a device on a network, such as 192.168.1.20.
  • Local address: the IP address your router gave a device in your home. It only works inside your home.
  • Public address: the IP address your home shows to the internet. Your friends use this one.
  • Router: the box that connects your home to the internet. Its own address is also called the gateway.
  • LAN (local area network): your home network. WAN (wide area network): the internet side of your router.
  • DHCP (Dynamic Host Configuration Protocol): the router feature that hands out local addresses.
  • MAC address (media access control address, also called the physical address): a built-in ID number on every network device. Your router uses it to tell devices apart.
  • TCP (Transmission Control Protocol) and UDP (User Datagram Protocol): two ways of sending data. The game tab says which one a port uses (some use both).

Where each step happens. Steps 1 and 5 happen on the server computer itself. Steps 2, 3 and 4 happen on your router's settings page, which you open in a web browser (the server computer is fine to use). Step 6 is a test with a friend. Each step tells you where you are at the top. First, we are going to find your server computer's addresses.

  1. On the server computer: find its addresses. You need three numbers from the computer, so write them down.
    1. Press the Windows key, type cmd, and open Command Prompt.
    2. Type ipconfig /all and press Enter.
    3. Find the section for the connection this computer uses (a cable is Ethernet; Wi-Fi is Wireless LAN). Write down: IPv4 Address (your local address, like 192.168.1.20; IPv4 is the common version of an IP, Internet Protocol, address; ignore the word "(Preferred)" after it), Default Gateway (your router's address), and Physical Address (the MAC, media access control, address: letters and numbers).
    A cable connection is usually steadier than Wi-Fi for a server. Wi-Fi and cable have different physical addresses, so write down the ones for the connection the server will use.
    Next step: we leave the server computer's settings and open your router's page.
  2. On your router's settings page: open it and log in.
    1. On the server computer, open a web browser. In the address bar, type the Default Gateway number from step 1 and press Enter.
    2. Log in. The login is often printed on a sticker on the router. If you changed it, use yours.
    3. Some routers (certain mesh systems, for example) use a phone app instead of a web page. The same settings exist there, but the names can differ.
    If the page will not open, try the address on the router's sticker, or search the router's brand and model plus "login". Do not change anything yet.
    Next step: on this same page, we make sure the server computer's address never changes.
  3. On your router's settings page: keep the server's address from changing. This is the DHCP (Dynamic Host Configuration Protocol, the router feature that hands out addresses) problem from earlier. Your router may hand the server computer a different address after a restart, which would break the rule you make in step 4. A reservation tells the router to always give this computer the same address.
    1. Look for a page or section called Address Reservation or DHCP Reservation. (Different brands use different names. Search your router's brand and model plus "address reservation" if you cannot find it.)
    2. Add a new reservation. Choose the server computer from the list of connected devices, or type its physical address (the MAC, media access control, address) from step 1. Use the local address the computer already has (the IPv4 Address from step 1).
    3. Save or apply.
    4. Restart the server computer. Then run ipconfig /all again (step 1) and check the IPv4 Address is the same. Some routers only apply a reservation the next time the computer reconnects, so this restart matters.
    Next step: still on the router's page, we add the door rule.
  4. On your router's settings page: add the port forwarding rule. This is the step that does the real work. Take it one box at a time.
    1. Find the right page. Common names: Port Forwarding, Virtual Server or NAT Forwarding (NAT is network address translation, how a router shares one internet connection). If you cannot find it, search your router's brand and model plus "port forwarding".
    2. Click Add (or New rule).
    3. Fill in the boxes. Their names change by brand, so here is what each one means:
      • Name (or description): anything you like, such as the game's name.
      • Protocol: TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), or "Both". Use what the game tab lists. If the game lists both and your router has no "Both", make two rules.
      • Port: some routers show two boxes, one called external (or public, or WAN: the wide area network, meaning the internet side) and one called internal (or private, or LAN: the local area network, meaning your home side). Put the game's port number in both. If there is only one box, put it once. If the game uses a range (for example 2456 to 2458), enter the first and last number.
      • IP address (or device): the server computer's local address from step 1.
      • Enabled: turn it on.
    4. Save or apply. Some routers restart to apply the change.
    5. Repeat for every port and protocol the game tab lists.
    Do not use an option called DMZ (demilitarized zone) or exposed host. It opens every door on the computer, not just the game's.
    If the rule is in and it still does not work, open the box at the bottom of this section.
    Next step: we go back to the server computer itself.
  5. On the server computer: allow the game through Windows Firewall. The firewall is a second guard on the computer itself. Even if the router lets a visitor in, the firewall can still turn them away. These steps are from Microsoft's own instructions for adding an inbound rule (a rule about visitors coming in).
    1. Press the Windows key, type wf.msc, and press Enter. A window called Windows Defender Firewall with Advanced Security opens. If Windows asks for permission, allow it.
    2. In the list on the left, click Inbound Rules.
    3. In the menu at the top, click Action, then New Rule.
    4. For the rule type, choose Custom, then Next.
    5. On the Program page, choose All programs, then Next.
    6. On the Protocol and Ports page, set the protocol to TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), whichever the game tab lists. Set the local port to the game's port number (Specific Ports, then type it; a range like 2456-2458 works). Then Next.
    7. On the Scope page, leave the defaults and click Next.
    8. On the Action page, choose Allow the connection, then Next.
    9. On the Profile page, tick the network types the rule applies to. Windows 11 treats a new network as Public by default, so for a home server tick Private and Public. (Domain is for work networks.) Then Next.
    10. Give the rule a name you will recognize, such as "Valheim UDP", then click Finish.
    11. Make one rule per protocol if the game uses both, and one per separate port if the game lists several.
    If you use antivirus software that has its own firewall, it has its own list. Allow the same ports there too.
    Next step: the test.
  6. Test it from outside your home.
    What does your friend connect to? They connect to your home's public address, the one the internet sees, plus the port if the game asks for one. They do not use the local address that starts with 192.168 (that only works inside your home). The router receives their knock on the door and, because of the rule from step 4, passes it to the server computer.
    1. Start the server (see Start your server below, or the game's own tab).
    2. On any device on your home internet, search what is my IP (IP is Internet Protocol). The number it shows is your public address.
    3. Check it against your router: open the router's status page (step 2) and find the Internet or WAN (wide area network) address. The two numbers should match. If they do not, open the box at the bottom of this section, because you are probably behind double NAT or CGNAT.
    4. Send your friend the public address (and the port, if the game asks for it; the game tab shows how to type it in).
    5. Ask a friend who is not on your home internet to try to join. Many games use UDP (User Datagram Protocol), and most port-check websites cannot test UDP, so a friend trying is the best test.
    You and the people in your home join with the server computer's local address instead. Some routers cannot send you to your own public address from inside your home.
    If friends who could join suddenly cannot, check your public address again. Your ISP (internet service provider) can change it from time to time.
More: if your router will not let you forward a port, or the test fails

My router won't let me forward a port, or friends still cannot join

First, the easy causes. The rule points at the wrong computer address, the type is wrong (TCP instead of UDP or the other way around), the firewall on the server computer is blocking it, or the router needs a restart to apply the rule.

Your ISP may be the problem. Some ISPs (internet service providers) block certain ports or limit what you can forward. A call or chat to them will tell you.

You may be behind double NAT or CGNAT. NAT (network address translation) is how a router shares one internet connection between your devices. Behind CGNAT (carrier-grade NAT), your ISP shares one public address between many homes. With double NAT, a second router sits in front of yours. Either way your home has no public address of its own to open doors on. With double NAT there are two walls, so the rule has to be made on the router in front too, or that router has to be switched to "bridge mode" so it stops being a second wall.

To check: find the "Internet" or "WAN" (wide area network) address on your router's status page and compare it to what a "what is my IP" website shows. If they are different, you are behind one of these. Addresses that start with 10., 192.168., 172.16 through 172.31, or 100.64 through 100.127 are private and are another sign.

What you can do: ask your ISP for a public address (some charge for it, some don't offer it), or, if a second router or modem of yours is in front, switch it to "bridge mode". If neither works, renting a server skips the problem.

RAM and CPU basics

RAM (random-access memory) is the computer's working memory. A server uses more of it as more players join, as the world grows, and as you add mods. If it runs short, the game lags or crashes.

CPU (central processing unit) is the part that does the thinking. Many game servers depend most on how fast a single core is, not on how many cores there are.

How much do you need? It depends on the game, the number of players and any mods. Each game tab and the hosting comparison show what real plans offer.

Signs you have too little: the game stutters or rubber-bands, players get kicked, or the server crashes when the world gets big. On a paid host you can usually upgrade the plan with a click.

How to see what your home server is using (Windows). Do this while the server is running with players on it. A quiet server tells you little. First, we are going to open Task Manager.

  1. Open Task Manager. Press Ctrl + Shift + Esc. (Or right-click the Start button and choose Task Manager.) If you only see a small window, click More details at the bottom.
    Next step: we look at the overall numbers.
  2. Look at the overall numbers. Click Performance in the list on the left. Click CPU: the big graph is how busy the processor is, as a percent. Click Memory: it shows how much of your RAM is being used.
    Next step: we look at the server by itself.
  3. Look at the server by itself. Click the Processes tab. Find the server program in the list (it is named after the game or its server tool; start the server and watch which entry appears). Click the Memory column heading to put the biggest memory users on top.

How to read it. These are rules of thumb. If Memory sits close to full while players are on, you need more RAM, or you need to close other programs. If the CPU graph is pinned at 100 percent, the processor is the limit. To check whether one core is the problem, right-click the CPU graph and choose Change graph to, then Logical processors. If one box is maxed out while the others are idle, the server is waiting on a single core.

Remember that a home server shares the computer with everything else running on it, including your own game if you play on the same machine.

You made it through the setup.

Start your server

This is the part you came for. The server is a separate download from the game you play. You download the server software, give it your settings (a name and a password), and start it. This section works for any game on Windows. Games hand out their server software in one of two main ways, so you pick the route that matches yours.

Only download server software from the game's own website or from Steam. Files from other sites can carry malware.

First, we are going to find out which route your game uses.

  1. Find out which route your game uses.
    1. Search for the game's name plus "dedicated server". Use the game's own website or help pages, not a random site.
    2. If that guide mentions Steam, SteamCMD or an app ID, use Route A, the next section.
    3. If the guide says to download a file from the game's website (a .zip, an installer or a .jar), use Route B.
    Next step: we pick up at the start of your route.

Route A: Steam games (SteamCMD)

SteamCMD is Valve's free, text-only version of Steam. It downloads server software straight into a folder you choose. It works the same for every Steam game, so you learn it once. These steps are for Windows. Wherever you see a capital-letter stand-in like MYGAME or APPID, type your own game's name or number instead. First, we are going to make two folders: one for SteamCMD itself and one for your server's files.

  1. On the server computer: make two folders.
    1. Open File Explorer and go to your C: drive.
    2. Make a folder named steamcmd (it will be C:\steamcmd).
    3. Make a folder named servers (C:\servers). Inside it, make a folder named after your game, such as C:\servers\MYGAME (use your own game's name instead of MYGAME).
    Short names with no spaces are easier to type into commands later.
    Next step: we download SteamCMD into the first folder.
  2. On the server computer: download SteamCMD.
    1. Open Valve's SteamCMD page and use its Windows download link. The file is called steamcmd.zip.
    2. Right-click the zip file and choose Extract All. Pick C:\steamcmd as the place to extract to.
    Next step: we find your game's server number.
  3. Find the server's app ID. Every Steam product has a number called an app ID. The server is its own product with its own number, not the same as the game's.
    1. Look in the game's official dedicated server guide first. It usually gives the number.
    2. If it does not, Valve keeps a Dedicated Servers List.
    3. Write the number down. This is your APPID in the next step.
    Next step: we download the server.
  4. On the server computer: download the server.
    1. Press the Windows key, type cmd, and open Command Prompt.
    2. Type the line below and press Enter. It moves Command Prompt into the SteamCMD folder:
    cd C:\steamcmd
    3. Type this line and press Enter. Before you do, replace APPID with your game's number and MYGAME with your folder's name:
    steamcmd +force_install_dir C:\servers\MYGAME +login anonymous +app_update APPID validate +quit
    Here is what the finished line looks like, using made-up values: if your game's number is 999999 and your folder is C:\servers\mygame, you would type this. Use your own number and folder, not these:
    steamcmd +force_install_dir C:\servers\mygame +login anonymous +app_update 999999 validate +quit
    What the pieces mean: force_install_dir is where the files go. login anonymous logs in without an account. app_update downloads the server (and updates it later). validate checks every file is correct. quit closes SteamCMD when it is done.
    4. Wait. The first time, SteamCMD updates itself and then downloads, which can take a while. When it finishes you are back at the Command Prompt.
    A few servers do not allow an anonymous login. If yours asks for an account, open the box at the bottom of this route.
    Next step: we find the file that starts the server.
  5. Find the file that starts the server.
    1. Open your server folder in File Explorer (for example C:\servers\MYGAME).
    2. The game's official guide names the file that starts the server. It ends in .exe (a program) or .bat (a batch file, a saved list of commands).
    3. If the guide does not name one, look for a file ending in .exe or .bat with "server" in its name.
    Do not start it yet. It needs your settings first.
    Next step: we set the server's name and password.
  6. Set the server's name and password. Servers read their settings from a file (or from launch options, which are extra words added to the start command). The official guide names the file and what goes in it, because every game does it differently.
    1. Open the settings file with Notepad (right-click it, then Open with, then Notepad).
    2. Fill in what the guide asks for. Typical settings are the server's name, a password, the world's name, and sometimes the port.
    3. Use a password you do not use anywhere else. Save the file.
    If the settings file is not there, the official guide says how to create it.
    Next step: we start the server.
  7. Start the server.
    1. Double-click the file you found two steps ago.
    2. A black window opens. This is the server's console, and it shows what the server is doing. Leave it open. Closing it stops the server.
    3. If the guide lists launch options, add them as it says.
    Next step: we check that it is really running.
  8. Check that it is running.
    1. Watch the console. The game's guide shows what its "ready" message looks like, because the wording is different for every game.
    2. If you see an error, copy the exact words. Searching them with the game's name often finds the fix.
    3. To let friends in, go back to Ports and port forwarding and finish the test in step 6.
    To update later, see Keeping your server updated. Do not just rerun the long command: it has validate in it, which can overwrite settings files you changed.
More: if SteamCMD or the server will not work

"steamcmd is not recognized"

Command Prompt is not in the SteamCMD folder, or the zip was not extracted there. Type cd C:\steamcmd and press Enter, then try the long command again. Check that the folder contains steamcmd.exe.

The server asks for a Steam account

Valve says some servers do not allow an anonymous login. In that case use a Steam account made only for servers, not your main one. Steam Guard may email you a code the first time. Type your login at the prompt SteamCMD shows, and do not save the password in a script or file.

The server window opens and closes at once

Start it from Command Prompt instead, so the message stays on the screen: type cd and your server folder, press Enter, then type the file's name and press Enter. Copy the error text it shows.

Route B: games that give you a download from their website

Some games hand you the server as a file from their own website. Minecraft: Java Edition is the best-known example, so we use it to show the pattern. Other games differ in the details, so check each game's own guide. We have not tested these steps ourselves yet. First, we are going to download the official server file.

  1. Download the official server file.
    1. On the server computer, make a folder such as C:\servers\minecraft.
    2. Open the official Minecraft server download page and download the server file. It is a .jar file (a Java program file). Downloading means you agree to Minecraft's license and privacy terms.
    3. Save it in the new folder.
    Next step: we check that Java is installed.
  2. Check that the right Java is installed. The Minecraft: Java Edition server runs on Java, and each Minecraft version needs a certain Java version.
    1. Press the Windows key, type cmd, and open Command Prompt.
    2. Type java -version and press Enter.
    3. Compare the number it shows with the table on the Minecraft Wiki's server tutorial. When we checked (September 2026), it listed Java 25 for Minecraft 26.1 and newer. These numbers change with new versions, so check the table for the version you downloaded.
    4. If you get an error, or the number is too old, install the Java version you need before you continue.
    Next step: we run the server once to set it up.
  3. Run it once and accept the license.
    1. In Command Prompt, move into the folder: cd C:\servers\minecraft
    2. Run the server. If your file is not named server.jar, use its name instead:
    java -jar server.jar --nogui
    3. It shuts itself down right away and creates two files, eula.txt and server.properties. That is normal on the first run.
    4. Open eula.txt with Notepad. Change eula=false to eula=true and save. Only do this if you agree to the Minecraft EULA (end user license agreement).
    Next step: we start the server for real.
  4. Start the server.
    1. Run the same line again: java -jar server.jar --nogui
    2. The first time, Windows may show a firewall prompt for "OpenJDK Platform binary". The Minecraft Wiki says that if you allow it for public and private networks, Windows manages the firewall rules for you.
    3. Leave the window open. It is the server's console, and closing it stops the server.
    4. The server's settings live in server.properties (open it with Notepad). The port is the server-port line, and the Minecraft Wiki lists the default as 25565.
    Next step: we let friends in.
  5. Let friends in. Go to Ports and port forwarding. In step 4, use port 25565. The Minecraft Wiki says to pick "TCP/UDP" or "Both" as the type (TCP is Transmission Control Protocol, UDP is User Datagram Protocol). Then finish the test in step 6.
    Optional: a start file. To start the server with a double-click, make a new text file in the folder named start.bat (in Notepad, choose Save as, set the type to All files) with these three lines:
    @ECHO OFF
    java -Xms1024M -Xmx2048M -jar server.jar --nogui
    pause
    The two numbers are the least and most RAM (random-access memory) the server may use, in megabytes (MB). Change them to fit your computer; see RAM and CPU.

Careful: a wrong change can stop your server working.

Changing a setting later

Game servers do not have a settings screen inside the game. Their settings live in a plain text file on the server computer. First, we are going to see the pattern, which is the same for every game.

  1. The pattern.
    1. Stop the server. Some games lose changes made while the server is running.
    2. Copy the settings file and rename the copy with today's date. That copy is your way back.
    3. Open the file with Notepad, change only the value, and save.
    4. Start the server and join it to check.
    5. If it works, keep the new file as your backup. If not, put the old one back.
    Next step: finding the file for your game.
  2. Where each game keeps its settings.
    Valheim: the long line in your copy of the start file. Dragonwilds: the file DedicatedServer.ini. 7 Days to Die: your copy of the settings file, myserver.xml. Minecraft: a file named server.properties in the server folder (the Minecraft Wiki's tutorial describes it). Each game tab has a section called Changing settings later with the exact steps and the choices we know about.

Switching hosts?

Moving your world between a paid host and your own computer

You can move a world from a paid host to your own computer, or the other way round. First, we are going to see what moving a world involves.

  • A world is saved as files. Moving it means copying those files from one place to the other, then telling the new server the world's name.
  • Every host has its own control panel. Look for a file manager, backups or FTP (File Transfer Protocol, a way to copy files to and from a server) page. If you cannot find it, ask the host's support how to download and upload your world.
  • Stop the server first, so no file is half-written. Copy, do not move, and keep your own backup.
  • Which files, and where they go, depends on the game. The game tabs for Valheim and Dragonwilds each have a section called Moving your world between a paid host and your own computer, with the exact files.
  • We have not tested moving a world between a host and a home computer.

Every time a game updates, come back here.

Keeping your server updated

Games update often. When a game updates, your players' copies of the game usually update by themselves. If your server stays on the old version, it can refuse them (players may see a message about an older or incompatible version). An update can also put some of the server's files back to how they came, which can wipe out settings you changed.

This section explains how to update safely and how to keep your settings. It works for any game. Each game's tab has the exact steps for that game. First, we are going to find out which way your server gets its updates.

  1. Find out how your server gets updates. There are three ways. You used one of them when you set it up.
    1. Installed through Steam (a tool in your Steam Library). Steam updates it, like it updates games.
    2. Installed with SteamCMD (Route A above). You update it by running a SteamCMD line again.
    3. Downloaded from the game's website (Route B above). You download the new file and swap it in.
    Next step: before any update, we make a backup.
  2. On the server computer: back up before you update. A backup is a copy of your files kept somewhere else, so you can put things back if an update goes wrong. Make one every time.
    1. Stop the server first. Click its black console window and close it the way your game's tab says (some games need Ctrl+C so the world saves).
    2. Find your world and save files. Your game's tab says where they are.
    3. Find the file where you set your server's name and password. That might be a .bat file, an .ini file or a properties file, depending on the game.
    4. Copy both into a new folder somewhere else, such as Documents\server-backups\2026-09-30 (use today's date). Copy, do not move.
    Next step: we keep your own changes safe from the update.
  3. Keep your settings in a file the update will not touch. The update can replace files that came with the game. Valve's SteamCMD page says that checking the files with validate "will overwrite any files that have been changed," and that files which are not part of the default installation are not affected.
    1. If you edited a file that came with the server, make a copy of it with a new name and keep your changes in the copy. Start the server from your copy.
    2. Keep one more copy of your edited file in your backup folder (the one from the last step).
    3. After every update, open your settings file and check that your name, world and password are still there.
    Next step: we do the update.
  4. Run the update. The server must be stopped first.
    1. Installed through Steam: open Steam on the server computer and go to your Library. Click the server tool. If it shows an update, let it finish. Steam also has a setting for each game or tool that controls when it updates. Right-click it, choose Properties, and look in the Updates section. The wording changes between Steam versions, so read the options and choose the one that keeps it up to date.
    2. Installed with SteamCMD: open Command Prompt (press the Windows key, type cmd, open it). Type the first line and press Enter, then replace MYGAME with your server's folder name and APPID with your game's number, and press Enter on the second:
    cd C:\steamcmd
    steamcmd +force_install_dir C:\servers\MYGAME +login anonymous +app_update APPID +quit
    Use the same folder and the same number you used when you installed. They are the MYGAME folder and APPID number from Route A. Example with made-up values: steamcmd +force_install_dir C:\servers\mygame +login anonymous +app_update 999999 +quit
    This line has no validate on purpose. Validate checks every file and can overwrite ones you changed. Only add it if the server is broken.
    3. Downloaded from the website: download the new file from the game's website, put it in the server folder in place of the old one, and keep your world and settings files. Check the Java version too (see Route B).
    Next step: we check that it worked.
  5. Check that it came back.
    1. Start the server the way you normally do.
    2. Look at your settings: the server name, world and password should be yours, not the defaults.
    3. Join the server from the game. If the game says the server is running an older version, the server did not update. Go back to the update step.
    4. If something looks reset, open the "More" box below.
    Optional: if you used SteamCMD, you can make the server update every time you start it. Open your start file (right-click it, then Edit) and put the update line from the SteamCMD step above the line that starts the server, then save. We have not tested this exact setup, so test it with a backup first.
More: if your settings or world look reset after an update

Your server name, world name or password went back to the defaults

The update probably replaced the original settings file. Your edits are not lost: open the copy you made, or the one in your backup folder, and put your name, world and password back in the file you start from. Then restart the server.

The server starts, but the world looks brand new

Most games make a new world when the world name in the settings does not match an existing one. If the settings went back to the default name, the server may have made a new, empty world. Your old world is usually still in the saves folder. Set the world name back to the old one, restart, and it should load. Do not delete anything until you have checked.

Players are told the server is on an older version

The server did not update, or was not restarted after updating. Stop it, run the update again, and start it.

The update stopped halfway or shows errors

Run the update again. If it still fails, copy the error text and search it with your game's name.

Still choosing a host? Compare hosting ›