Vintage Story Dedicated Server Setup Guide (2026)

Vintage Story shines when you build a world that lasts longer than one session. Hosting on Open to LAN works for a night with friends, then falls apart the moment you log off. 

A vintage story dedicated server keeps your world online, even when your game is closed. Your world stays available 24/7 for anyone who joins next.

You also gain real control over rules, mods, backup plans, and who can log in. You can run the server on your own PC, a spare box, or rented hardware, as long as your CPU, RAM, and upload speed are strong enough. 

This guide walks you through every step: planning, installation, ports, safe settings, mods, performance, and recovery. If you want your group to treat this world as home, not a throwaway save, keep reading.

Key Takeaways

• Vintage Story is multiplayer, and a dedicated server keeps your world online when you log off.
• You only need a strong CPU, sufficient RAM, an SSD, and a stable internet connection. You do not need a GPU for the server.
• If you have 3–4 or more regular players or mods, consider moving from “Open to LAN” to a dedicated vintage story server.
• Small friend group → self-host. Mid-size modded group → good game host or small VPS. Large or public world → strong VPS or dedicated server.
• Aim for 3–4 GB RAM and at least 5 Mbps upload for a small group. Use wired Ethernet on the server.
• Install on Windows or Linux, set a clean data folder, and test on LAN before you open the server to the internet.
• For outside players, either forward port 42420 or skip router work by using a VPN mesh or paid game hosting.
• Keep settings simple at first, add mods slowly, and run daily backups so you can recover from crashes or bad changes.

Understand Vintage Story Multiplayer Options

Is Vintage Story Multiplayer? Yes. Vintage Story supports full multiplayer with several hosting options. You choose how simple or stable you want your sessions to be.

Main Multiplayer Modes

• Single-player
  • One player, local world only.
  • Good for testing and learning.
• Local LAN / Open to LAN
  • Start a world and click Open to LAN.
  • Friends on the same router join via your local IP.
  • The world is online only while your game runs.
• Open to the Internet in-game
  • The game tries to expose your world over the internet.
  • Friends join using your public IP.
  • Still tied to your PC and your session.
• Dedicated server
  • Separate server process on your PC, a spare box, or hosting.
  • World stays online when you close the game.
  • Easier to manage mods, roles, and backups.

When to Move to a Dedicated Server

Switch to a dedicated server when:

• You have 3–4+ regular players.
• You use or plan a modded setup.
• You want the world online when you are offline.
• You do not want to share your gaming PC IP with guests or viewers.

From this point on, the guide focuses on that dedicated path.

Check Vintage Story Server Requirements

Before you install anything, make sure the machine can handle it.

Core Hardware Rules

• CPU
  • Favour strong single-thread speed.
  • At least 4 threads for small groups.
• RAM
  • Base: about 1 GB for the world.
  • Add about 300 MB per active player.
  • Add extra headroom for heavy mods.
• Disk
  • Use an SSD, not an HDD.
  • Keep enough space for the world plus backups.

Example Sizing

2–4 vanilla players

• CPU: mid-range modern CPU with 2–4 threads free.
• RAM: 3–4 GB for the server.
• Disk: 10–20 GB free on SSD.

5–10 light-modded players

• CPU: 4–8 threads free.
• RAM: 4–8 GB for the server.
• Disk: 20–40 GB free on SSD.

10–30 modded players

• CPU: 8+ threads free.
• RAM: 8–16 GB for the server.
• Disk: 40–80 GB free on SSD.
• At this stage, think VPS or dedicated hardware, not your main PC.

Network needs

• Upload speed
  • 2–4 players: aim for 5 Mbps upload.
  • 5–10 players: 10–20 Mbps upload.
  • 10–30 players: 25 Mbps or more.
• Connection type
  • Use wired Ethernet on the server.
  • Avoid Wi-Fi for the server machine.

If your home line cannot meet this, a host with vintage story dedicated server hosting in a nearby region will feel smoother.

Software Requirements

• .NET runtime
  • Install .NET Runtime 8.0. On Windows, .NET Desktop Runtime 8.0 also works and includes the Runtime.
• OS support
  • Windows: a supported version with current patches.
  • Linux: a modern LTS distro with a new enough GLIBC.

If your system is too old to meet this, upgrade the OS before you continue.

Choose Your Hosting Model

Quick recommendation

• Small friend group → self-host.
• Mid-size modded server → good game host or small VPS.
• Large or public server → strong VPS or dedicated server near your players.

Prepare Your Network and IP

You only need three things: the right IP, a stable local address, and an open port.

Local vs public IP

• Local IP (like 192.168.x.x or 10.x.x.x):
  • Used inside your home network.
  • Friends on the same router use this to join.
• Public IP:
  • Given by your ISP.
  • Friends outside your home use this.

You test on local IP first. You share the public IP only when you go online.

Give the Server a Static Local IP

Do not let the router change the server’s address.

• In the router:
  • Open DHCP or LAN settings.
  • Reserve a fixed IP for the server’s MAC address.
• Or on the server:
  • Set a manual static IP in Windows or Linux that matches your LAN range.

Write this IP down. You will use it for port forwarding and LAN tests.

Firewalls

• On Windows:
  • Add an inbound rule for port 42420 TCP and UDP, or for the server EXE.
• On Linux:
  • With ufw: allow 42420/tcp and 42420/udp.
  • With firewalld: open the same ports in the correct zone.

Vintage Story Ports

• Default port: 42420.
• Use TCP (and also UDP on 1.20+).

You will:

• Keep 42420 in your config (unless you have a conflict).
• Allow 42420 in the OS firewall.
• Forward 42420 in the router to the server’s local IP in a later step.

Quick Pre-flight Check

Before you touch port forwarding, confirm:

• The server has a fixed local IP.
• The OS firewall allows 42420 TCP (and UDP on 1.20+).
• You know how to log into your router.

If all three are true, you are ready to install and test the server.

Windows Vintage Story Dedicated Server Setup

Now you create a clean install, a data folder, and a simple start method.

1. Install The Game to a Clean Path

• Run the Vintage Story installer.
• Pick a folder like C:\VintageStory or D:\VintageStory.
• Avoid C:\Program Files and other system folders.

This path holds the server EXE and game files.

2. Create a Server Data Folder

• Make a folder such as D:\VS-Server-Data.
• This will hold:
  • Worlds.
  • serverconfig.json.
  • Logs and backups.

Keeping server data separate stops it from mixing with single-player saves.

3. Run the Server Once

• Open your game folder.
• Run VintagestoryServer.exe one time with no extra flags.
• Wait for it to finish loading and start listening on a port.
• Type /stop in the console.

This first run creates default config files. Note where serverconfig.json sits if it still uses the default data path.

4. Create a Shortcut or Batch File

Shortcut:

• Right-click VintagestoryServer.exe → Create shortcut.
• Open the shortcut properties.

In Target, append (include one space before –dataPath):
–dataPath=”D:\VS-Server-Data”

• Move the shortcut to your desktop.

Batch file (optional):

Create start-server.bat in the game folder:

@echo off

cd /d C:\VintageStory

VintagestoryServer.exe –dataPath=”D:\VS-Server-Data”

pause

Double-clicking either will start your Windows vintage story server setup with the right data folder.

5. Test on LAN

• Start the server with your shortcut or batch file.
• On the same PC:
  • Open the game → Multiplayer → Add server.
  • Address: localhost:42420.
  • Join and confirm it loads.
• On another PC on the same router:
  • Use the server’s local IP, for example 192.168.1.50:42420.
  • Join and confirm it works.

If both tests pass, your Windows server is ready for port forwarding and external access in later steps.

Linux Vintage Story Dedicated Server Setup

This is your base vintage story dedicated server linux flow.

1. Create a User and Folders

• SSH into your Linux server.
• Create a user:
  • sudo useradd -m -s /bin/bash vintagestory
  • sudo passwd vintagestory

• Log in as that user:
  • sudo su – vintagestory

• Create folders:
  •  mkdir -p ~/vs-server
  • mkdir -p ~/vs-data

2. Install Prerequisites

For Ubuntu / Debian:

• sudo apt update
• sudo apt install -y wget unzip screen
• # Install .NET Runtime 8.0

Make sure the .NET runtime version matches the current server build.

3. Download and Unpack the Server

From the vs-server folder:

• cd ~/vs-server
• # Download the latest Linux x64 server package from https://www.vintagestory.at/selfhosting/
• tar -xzf vs_server_linux-x64_*.tar.gz

You should now see VintagestoryServer.dll and related files in ~/vs-server.

4. First Run With a Data Path

Run the server once to generate configs:

• cd ~/vs-server
• dotnet VintagestoryServer.dll –dataPath ~/vs-data

Let it finish startup, then type /stop in the console.

This creates serverconfig.json and world folders inside ~/vs-data.

5. Optional: systemd Service

If you want the server to start on boot:

• sudo nano /etc/systemd/system/vintagestory.service
• Example unit:

[Unit]

Description=Vintage Story Server

After=network.target

[Service]

User=vintagestory

WorkingDirectory=/home/vintagestory/vs-server

ExecStart=/usr/bin/dotnet VintagestoryServer.dll –dataPath /home/vintagestory/vs-data

Restart=on-failure

RestartSec=10

[Install]

WantedBy=multi-user.target

Then:

sudo systemctl daemon-reload

sudo systemctl enable vintagestory

sudo systemctl start vintagestory

6. LAN test

Check status:

sudo systemctl status vintagestory

• From a PC on the same network, add a server in-game using the Linux host’s local IP, for example, 192.168.1.60:42420.

If you can join, your Linux vintage story server setup works on LAN.

Port Forwarding and External Access

Now you move from LAN only to a system where friends can join from outside.

1. Confirm LAN Before Anything

Only continue if:

• You can join with localhost:42420 on the host itself.
• You can join from another device on the same router using the local IP.

If this fails, fix it before touching your router.

2. Classic Port Forwarding

On your router:

• Log in to the router web UI.
• Find Port Forwarding, Virtual Server, or similar.
• Add a rule:
  • External port: 42420
  • Internal port: 42420
  • Protocol: TCP + UDP (or Both)
  • Target IP: your server’s static local IP (for example 192.168.1.50)

Save and apply.

3. Test External Access

• Find your public IP from a what is my IP site.

Give friends the address in this format:

<your_public_ip>:42420

Ask someone outside your network to join while the server runs.

If they cannot join:

• Recheck the port rule and target IP.
• Make sure the OS firewall still allows 42420.
• Ask your ISP if you are behind CGNAT (carrier NAT). If yes, see below.

4. UPnP Option

Vintage Story can try UPnP on some routers:

In the server console, run:

/serverconfig upnp 1

Restart the server.

This only works if your router supports UPnP and your ISP setup allows it. Treat it as optional, not a guarantee.

5. When Port Forwarding is Impossible

If you are behind CGNAT, locked ISP hardware, or strict rules:

• Use a VPN mesh tool:
  • Tailscale.
  • ZeroTier.
• Install the client on the server and on each player’s PC.
• Share the VPN IP and connect through that instead.

6. Basic Safety Rules

• Do not expose RDP, SSH, or other admin ports to the public by mistake.
• Use a server password or whitelist if you do not want random players.
• If you open your server to the public list, keep backups and logs in good shape.

Core Server Settings (serverconfig)

Once the server runs, you tune vintage story server settings in serverconfig.json or through commands.

1. Where to Find Serverconfig

• Windows: inside your chosen –dataPath folder.
• Linux: inside the data folder you passed to –dataPath (for example ~/vs-data).
• Game panels: look for a Configuration or serverconfig editor in the panel.

Always stop the server or know how live edits behave before changing the file.

2. Identity and Basic Info

Key fields:

• ServerName
• ServerDescription
• WelcomeMessage
• ServerLanguage

Keep these short and clear. They help players recognise your server in lists.

3. Access Control

Main settings:

• Port: keep 42420 unless you have a conflict.
• MaxClients: set this to match your hardware, not your dreams.
• Password:
  • null or empty = open access.
  • Set a string to require a password.

For a private server, use a password or whitelist. For a public world, combine clear rules with strong admin control.

4. Whitelist and Visibility

Two main ideas:

• Whitelist
  • Only listed usernames can join.
  • You manage this with commands or panel tools.
    Note: dedicated servers are whitelisted by default (WhitelistMode=default), so add friends before testing.
  • Good for small, trusted groups.
• Advertise / public list
  • A flag that lets the server show up on the global server browser.
  • Only enable this when you are ready to host strangers and have backups in place.

Together, these define who can see and join your vintage story dedicated server.

5. Time, Pause, and Gameplay Basics

Common options:

• Pause when empty:
  • Decide whether world time passes when no one is online.
• Day length/time speed:
  • Shorter or longer days, depending on your group.
• PvP toggle:
  • Turn player damage on or off.
• Other survival tweaks:
  • Food spoil rate, death penalties, etc., depending on how hardcore you want the server.

Start close to default. Change one thing at a time and see how players react.

6. Roles and Permissions (high level)

The server has simple role levels, such as:

• Guest.
• Player.
• Moderator.
• Admin.

You grant and revoke roles with commands or panel tools. Keep admin roles limited and logged.

7. Applying and Testing Changes

• For small edits, use /serverconfig commands where possible.
• For file edits:
  • Stop the server.
  • Edit serverconfig.json.
  • Save and restart.

After each change:

• Join the server.
• Check that settings behave as expected.
• Watch the console for warnings or errors.

Once you have solid serverconfig values, you can move into world generation and deeper tuning in the next steps.

World Generation and Map Design

World size and shape decide how your server feels and how heavy it is.

Default World Scale

By default, Vintage Story creates:

• Very large horizontal size.
• 256 block height.
• Mixed terrain with oceans, mountains, and ruins.

Great for long runs, heavy for weak hardware.

Pick a World Size That Matches Your Group

Small co-op (2–6 players)

• Use a smaller map.
• Aim for a few thousand blocks across.
• Players meet each other more and chunks stay warm in memory.

Community server (10–20+ players)

• Use a larger map with room to spread.
• Pick a size that your CPU and RAM can handle during peak hours.
• Consider pruning old, empty regions once in a while.

Shape and Difficulty

Before you start the world, decide:

• More land or more water.
• Flat terrain for builders or rough terrain for survival.
• Harsh climate or softer conditions for casual groups.

You set these in the world config or panel presets. Start close to default for your first vintage story server setup, then adjust on the next world after feedback.

World Size vs Performance

Larger worlds mean:

• More chunks on disk.
• More cost during saves and pregen.
• More RAM used when players spread out.

If you see lag during saves or constant high RAM use, go smaller next wipe or reduce travel beyond a set radius.

Core Server Commands You Actually Need

You do not need a full command list. You need a small set you will use weekly.

Use these in:

• The server console window.
• In-game chat with a leading / if your role allows it.

Server Control

• /autosavenow
  • Force a manual save.
• /stop
  • Shut down the server cleanly.
• /announce <message>
  • Send a broadcast message to all players.

Player Control

• /kick <player> <reason>
  • Remove a player from the server.
• /ban <player> <number> <hour|day|week|year> <reason>
  • Ban a player for a set timespan (you can unban early).
• /unban <player>
  • Remove a ban.
• /op <player>
  • Give admin powers.
• /player <player> role suplayer
  • Remove admin powers (set role back to suplayer).
• /player <player> gamemode <mode>
  • Show or set a player’s game mode.
• /tp <player> <x> <y> <z>
  • Teleport a player.

These are your core vintage story dedicated server commands for daily admin work.

Whitelist and Access

• /player <player> whitelist on
• /player <player> whitelist off

Use these when you run a closed, invite-only world. This pairs with your vintage story dedicated server whitelist settings in serverconfig.

Simple debug and health checks

• Command or panel button to see online players.
• Command to print TPS or basic performance data (varies with version).

Use them when players report lag so you can see whether the issue lives on the server or their side.

Mods on a Vintage Story Dedicated Server

Mods change how your world plays and how heavy it is. Treat them as part of server design, not just decoration.

Mod Types

Three broad types:

• Client-side only
  • UI or visual changes.
  • Do not affect the world state.
• Server-side only
  • Automation, progression, extra rules.
  • Installed only on the server.
  • Clients download what they need on join.
• Both client and server
  • Must match on both sides.
  • The game prompts players to sync when they connect.

Know which type you install so you do not chase false errors.

Where to Get Mods

Use trusted sources:

• Official mod site.
• Well-known community hubs and forum posts.

Avoid random file-share links. They may be outdated or unsafe.

How to Add Mods to Vintage Story Dedicated Server (Self-Host)

On a self-hosted machine:

1. Stop the server.
2. Download the mod .zip file.
3. Place it in the Mods folder inside your server data path.
4. Start the server and watch the console for errors.

If the server starts clean, join in-game and confirm the mod works.

Mods on Game Panels

On a host with a panel:

• Use the file manager or SFTP to upload .zip files into the Mods folder.
• Some hosts add one-click installers for popular mods.
• Always restart the server after changes and check the log.

Ask support if the panel changes the mod folder path; some do.

Modpacks and Order

When you plan a full set of vintage story dedicated server mods:

• Make a list of all mods and versions.
• Start with core libraries and required frameworks.
• Test on a fresh world first.
• Keep a backup before adding or removing major mods mid-season.

Handling mod issues

If you see crashes or odd behaviour after adding a mod:

• Stop the server.
• Remove the last mod you added or disable it.
• Start again and see if the issue goes away.
• If a world corrupts, restore from the last good backup.

Keep your mod list tight. Every extra mod costs RAM, CPU, and admin time.

Performance Tuning and Stability

You always tune after the server runs and people start playing. Start with defaults, then adjust.

Main Settings That Matter

Focus on a few levers:

• View distance/chunk radius
  • Lower value = less CPU and RAM per player.
  • Small friend group: keep it modest.
  • Big public world: keep it tight to avoid load spikes.
• Autosave interval
  • Short interval = safer data, more short pauses.
  • Default is 5 minutes; try 10–15 minutes only if saves stutter.
  • Go longer only if saves cause visible stutter.
• Entity and animal counts
  • Too many animals or dropped items hurt performance.
  • Run clean-up commands if counts explode.
  • Keep farm and mob farms under control.

Simple Profiles

Use these as starting points:

• Small group (2–6 players)
  • View distance: medium.
  • Autosave: 10–15 minutes.
  • Restarts: once per day.
• Busy community (10–30 players)
  • View distance: lower.
  • Autosave: 20 minutes.
  • Restarts: once or twice per day.
  • Watch entity counts often.

Watch the Host, Not Just the Game

Check:

• CPU load during peak time.
• RAM usage over a full evening.
• Disk busy time during saves.
• Network usage when many people join at once.

If the machine sits near 100% CPU or runs out of RAM, dial back settings or move the vintage story dedicated server to stronger hosting.

Security, Backups, and Updates

You protect the world first. Then you think about new features.

Control Who Gets In

Use these tools together:

• Password
  • Quick barrier for friends-only worlds.
• Whitelist
  • Add known players only.
  • Best for small private servers.
• Roles
  • Keep admin rights for very few people.
  • Give moderators just enough power to keep order.

Never give console access or full admin to strangers.

Backups

Backups save you from corrupt chunks, bad mods, and griefing.

Aim for:

• Frequency
  • At least once per day.
  • More often on active servers.
• Retention
  • Keep several days of backups.
  • Keep at least one older snapshot for long-term fallback.
• Location
  • Store backups away from the live world folder.
  • For hosts: use panel backups and off-site downloads.
  • For self-host: copy to another drive or a cloud bucket.

Test a restore once so you know the process works.

Safe Updates

When you update the game or mods:

1. Announce a short maintenance window.
2. Make a fresh backup.
3. Stop the server cleanly.
4. Update the server files.
5. Update mods to supported versions.
6. Start the server and check logs.
7. Ask one or two players to test key areas.

If you see crashes or broken worlds, roll back to the pre-update backup and wait for fixes.

Launching and Growing Your Server Community

Once the tech works, you make the server worth logging into.

Soft Launch

• Start with a small group of friends.
• Run for a week before you invite more people.
• Fix obvious issues: spawn, food access, basic rules.

This phase gives you clean feedback with less drama.

Clear Rules

Write short rules that players can remember:

• Griefing policy.
• PvP policy.
• Land claim use.
• How you handle theft and disputes.

Put them in:

• The server description.
• A spawn sign or book.
• A pinned post in your Discord, if you run one.

Use Simple Community Tools

• Create a Discord or similar space.
• Add channels for:
  • Announcements.
  • Bug reports.
  • Trade or screenshots.

Point new players there from the server MOTD or welcome message.

Adjust Based on Behaviour

Watch how people actually play:

• If players spread too far, reduce world size in the next season.
• If griefing becomes common, tighten claims, whitelist, or add mods that help.
• If early game feels too slow for regulars, tweak settings or add light QoL mods.

Small changes work better than big swings that reset everything without warning.

Troubleshooting Cookbook

Use this as a quick map from problem to likely causes.

When in doubt

If you feel lost:

• Check server logs from the last start.
• Revert the last change you made.
• Test with a fresh, empty world to see if the issue is world-specific.

Once the server runs clean on a fresh world, you know the problem lives in the old world, settings, or mods, not in the core setup.

When Your Vintage Story Server Outgrows Home Hosting

At some point, the problem is not your config. It is the platform. Home upload dips. Wi-Fi spikes. The host PC reboots. Players feel it fast.

If you want a stable Vintage Story dedicated server, moving to RedSwitches is a clean next step.

Here is what helps in real terms:

• 99.99% SLA-backed uptime keeps the world reachable when your group plays on a schedule.
• Always-on network-level DDoS protection helps if you list your server publicly or share the IP widely.
• 20+ data-center locations lets you host close to players for lower latency.
• Full root access + OS choice makes .NET installs, firewall rules, mods, and backups simple.
• Public IPv4 included means outside players can connect cleanly without weird workarounds.
• Many plans include IPMI/KVM so you can recover even if the OS fails to boot.
• NVMe/SSD options with 10Gbps and 25Gbps unmetered bandwidth tiers give you headroom as your world and mod list grows.

Do it the safe way. Backup your dataPath. Deploy the server. Open port 42420. Test with one friend. Then invite everyone.

FAQs

Q. Is Vintage Story multiplayer and how do I host for friends?

Yes. Vintage Story supports full multiplayer. For a few friends you can:

• Use Open to LAN if everyone shares the same router.
• Use Open to Internet for short sessions with distant friends.
• Or run a small dedicated server on your PC and share your public IP and port.

If you plan to play together often, set up a small dedicated server and either port forward once or use a simple VPN mesh (Tailscale / ZeroTier) so you never touch the router again.

Q. Do I need a GPU for a vintage story dedicated server?

No. The server runs headless and does not render graphics. You care about:

• CPU single-thread speed.
• Enough RAM.
• SSD storage.
• Stable upload.

You only need a GPU if you play the game on the same machine you use as the server.

Q. What is the easiest path if I hate port forwarding?

Three options:

• Rent vintage story dedicated server hosting from a game host. They handle ports and firewalls.
• Use a VPN mesh (Tailscale, ZeroTier). Everyone joins the same private network and connects to the VPN IP. No router changes.
• Use in-game Open to Internet and see if your router supports it. This can work but stays less reliable than the first two.

If you want long-term ease, a panel host or VPN mesh is usually the least painful route.

Q. Can I run a vintage story dedicated server on a Raspberry Pi or ARM board?

Yes, but with limits.

• Use a 64-bit OS and a board with at least 4 GB RAM (Pi 4/5 or similar).
• Install the required .NET runtime for ARM.
• Expect to host 2–4 vanilla players at best.
• Avoid heavy modpacks and large worlds.

Treat it as an experiment or a tiny friends server, not a serious public host.

Q. How many players can I host with 4 GB RAM?

Use this rough rule:

• About 1 GB base for the world.
• About 300 MB per active player.
• Plus some headroom for the OS.

With 4 GB total, expect:

• 3–4 players with mods.
• 4–6 players on a light or vanilla setup.

If you want 8+ regular players, move to 6–8 GB RAM or higher.

Q. How do I migrate from game panel hosting to my own VPS or dedicated server?

Simple pattern:

1. Set up Vintage Story on your new VPS or dedicated box and confirm a clean test world runs.
2. On the old panel host, stop the server.
3. Use SFTP or the panel file manager to download your world and data folder (worlds, serverconfig, permissions).
4. Copy those files into the dataPath folder on your new server.
5. Update serverconfig if needed (name, advertise, port).
6. Open port 42420 on the new firewall and router (if self-hosted).
7. Start the new server and test with one or two players before you tell everyone else.

Once the new host runs smoothly, retire the panel server.