Free tools Windows power users keep installed
One-click scans. No signup required.
Stop the server cleanly, back up the persistent data directory, replace only the Vintage Story server application files, then restart and verify the world, mods, and player connections. Keeping the replaceable program files separate from the data directory is the key protection against losing saves or settings.
Godlike.Host offers hosted Vintage Story servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What an update changes—and what it must not
A Vintage Story dedicated server has two different kinds of files. The application installation contains the executable, .NET assemblies, libraries, assets, and launch scripts supplied by a particular game release. The persistent data directory contains the worlds, saves, server settings, player data, and usually the installed mods. An update should replace the first group while preserving the second.
As an Amazon Associate I earn from qualifying purchases.
The Vintage Story Multiplayer Server guide warns that installing a newer version requires removing the old installation files first, because leaving them in place can produce unpredictable behavior. The same guidance warns not to delete a data folder located inside the installation directory: it may contain your save games, settings, and player data. Before deleting or replacing anything, identify which directory contains the world and configuration files.
The safest layout is a replaceable application directory beside a persistent data directory. For example, a Linux host might use /srv/vintagestory/server for application files and /srv/vintagestory/data for worlds and settings. On Windows, choose a similar arrangement such as C:VintageStoryserver and D:VintageStoryData. The exact paths do not matter; the separation does.
#1 Best Overall
- ENTERTAINING AND UNEXPECTED QUESTIONS: This handy box is filled with 140 surprising and engaging prompts to inspire reminiscences between family, friends, or couples!
- FAMILY GAME NIGHT FUN: A special way to inspire intergenerational sharing. Great family game for kids and adults.
- TAKE IT ANYWHERE: The portable box is the ideal size to throw in your bag to take on vacation or to a family get-together.
- A FUN GIFT: Perfect for game night enthusiasts; kids, parents, and grandparents wanting to connect across the generations; anyone in search of birthday presents, anniversary gifts, or stocking stuffers for adults, teens, or the whole family.
- EXPLORE THE ENTIRE SERIES: This game is part of the Games Room series, a collection of elegantly designed, geometrically patterned small boxes filled with engaging games to inspire lively conversation and endless laughs.
Check requirements before scheduling maintenance
Updating is easier when you know the server’s current version, launch command, data path, mods, and network settings. Record these details before taking the server offline.
| Item | Published guidance or value | Why it matters during an update |
|---|---|---|
| Memory | 1 GB base RAM plus 300 MB per connected player, a conservative recommendation in the Vintage Story dedicated-server guide | Large worlds, many players, or heavy mods may require more; watch memory use after the update rather than treating the figure as a hard limit. |
| CPU | Four CPU threads recommended | World generation and modded workloads can make an otherwise successful update appear faulty if the host is already CPU-bound. |
| Network port | TCP and UDP port 42420 | Preserve firewall rules, router forwarding, and VPN rules while replacing the application. |
| Windows launch | VintagestoryServer.exe, preferably with a separate --dataPath |
Prevents the dedicated server from mixing its data with single-player files. |
| Linux launch | dotnet VintagestoryServer.dll --dataPath /path/to/data |
Makes the persistent location explicit when the application directory is replaced. |
| ARM64 | Supported experimentally according to the dedicated-server guide | Recheck compatibility and mod support for the exact ARM operating system and hardware. |
No current release number should be assumed from a guide or an old setup note. Select the version you actually intend to run from your Vintage Story account or the official download area, and make sure every player knows the maintenance window.
The safe update sequence
Use this sequence for a normal release update, whether the host runs Windows or Linux.
- Announce maintenance. Tell players when the server will close, which game version you are installing, and when they can test access again. Ask players not to leave clients connected while the server is stopping.
- Stop the server cleanly. Use the server console’s normal shutdown command or stop the service that launched it. Do not replace files while the process is writing a save. Wait until the process exits and the console or service manager confirms it has stopped.
- Record the current state. Write down the running server version, launch command, data path, operating-system details, and any custom changes to
serverconfig.json. Save a copy of the current mod list, including each mod’s version and dependency notes. - Back up the persistent data directory. Copy or snapshot the complete directory containing worlds, saves, configuration, player data, and mods. Keep the backup on a different disk or host when possible. Name it with the date and old game version so you can identify it during rollback.
- Check mod compatibility. For every mod, verify support for the target Vintage Story version, required dependencies, and whether it is server-side, universal, or client-side. Download updated files before taking the server offline if the mod author requires a newer release.
- Replace only application files. Remove or move the old installation payload, then extract or install the intended release into the application directory. Do not delete the separate data directory. If data is nested inside the old installation, move it to a protected location first or exclude it explicitly from the replacement operation.
- Restore the launch configuration. Keep the same
--dataPath, service definition, environment variables, firewall rules, and server configuration unless the new release requires a documented change. Editserverconfig.jsononly while the server is stopped. - Start and observe. Launch the server and read the console or log from the first line. Look for migration notices, missing assets, dependency failures, permission errors, or a different data path than expected.
- Verify before reopening. Log in as an administrator, inspect the world, test a normal player account, and confirm that the intended mods load. Test from inside the local network and from an external connection if the server is public.
- Retain rollback material. Do not delete the old application files or dated data backup until the world has loaded, players can connect, and the server has operated normally through at least one save cycle.
Updating on Windows
Use a dedicated data path
The Windows server can be launched with a separate data location. A typical shortcut, batch file, or service command points to the executable and supplies the path explicitly:
VintagestoryServer.exe --dataPath D:VintageStoryData
Rank #2
- HOWDY PARTNER - Welcome to Disney Pixar Toy Story Obstacles & Adventures, the cooperative deck-building game that brings the world of Toy Story to life! Play as your favorite characters from the films - Sheriff Woody, Buzz Lightyear, Jesse, Rex and Bo Peep
- TO INFINITY, AND BEYOND - This family board game features artwork, characters, obstacles, and adventures from across all the Toy Story movies and television films - Toy Story, Toy Story 2, Toy Story 3, Toy Story 4, Toy Story of Terror!, and Toy Story That Time Forgot
- THERE'S A SNAKE IN MY BOOT - Watch out for the hazards and obstacles that try and end playtime, While the toys may be cute, don't let them deceive you as there are serious challenges along the way
- YOU'VE GOT A FRIEND IN ME - Work together in this cooperative group game as you build your deck and move along the 6 sequential games that build on their level of difficulty
- 2-5 players | Ages 8+ | 30-90+ Min Play Time
Use the path that contains this server’s worlds and configuration, not a path used by a desktop client’s single-player installation. If you have never specified --dataPath, stop the server and inspect its current working directory before changing anything. Moving data without updating the launch command can make the new server appear empty even though the world still exists.
Replace the application safely
- Stop the console window, scheduled task, or Windows service that runs
VintagestoryServer.exe. - Copy the complete data path to a dated backup location. Include the mod directory and
serverconfig.json. - Rename the old application directory, for example by appending the old version, instead of deleting it immediately. This gives you a quick rollback.
- Extract the new Windows server files into a clean application directory.
- Update the shortcut, batch file, or service only if the executable path changed. Keep the same
--dataPathargument. - Start the server and watch the console until it finishes loading. Confirm that the expected world name and player data appear.
Windows Defender Firewall may create a new rule when the executable path changes. If local players can join but internet players cannot, check that the new VintagestoryServer.exe is allowed and that TCP and UDP port 42420 are still forwarded to the correct machine.
Updating on Linux
Protect data before removing installation files
The official Linux pattern is to download the server-only Tar.gz Archive/Linux (server only) package from the Vintage Story account or download area and extract it. The guide’s instruction to remove old installation files applies to the application payload, not to a data directory that contains saves.
For a clean layout, stop the service and make a dated copy of the data directory, then place the new archive in a temporary download location. An illustrative extraction sequence is:
sudo systemctl stop vintagestory
sudo cp -a /srv/vintagestory/data /srv/backups/vintagestory-data-2026-10-15
sudo mv /srv/vintagestory/server /srv/vintagestory/server-old
sudo mkdir /srv/vintagestory/server
sudo tar -xzf vintage-story-server.tar.gz -C /srv/vintagestory/server
Recommended Free Tools
Rank #3
- A WHOLE NEW WAY TO PARTY: Skip the small talk and spark unforgettable conversations with It’s Kind of a Fun Story, the adult party game where the story of your life earns you points. Perfect for adult game nights, pre-games, happy hours, bachelorette parties, or family gatherings.
- EASY TO LEARN, FUN TO PLAY: Take turns drawing cards and answering questions to be the first player to earn seven points! Story Cards put you in the spotlight to tell a story from your life, but watch out, if another player thinks they have a better tale, they can play a Hear Me Out Card to try to steal your points. Left or Right, Point a Finger, and Everybody Answers cards keep every round fresh, fast-paced, and full of surprises.
- FUN, HEARTFELT, AND FULL OF CONNECTION: With 320 conversation cards, every round is unique, hilarious, and full of exciting stories. More than just a funny adult card game, it brings people closer: laugh together, share embarrassing memories, and bond over stories that are silly, surprising, or even deep.
- CUSTOMIZE YOUR VIBE: Keep it clean or make it spicy with the included R-Rated mini-expansion pack. Clearly marked R-Rated cards let you adjust to your group, and every player gets a Nope Card to skip any topic they’re not comfortable with. Everyone stays engaged and having fun. Perfect as a drinking game, icebreaker game, or casual conversation game.
- PERFECT FOR EVERY OCCASION: Ideal for friends’ game nights, family gatherings, pre-games, happy hours, bachelorette parties, or adult game nights. It’s Kind of a Fun Story is the ultimate adult storytelling card game that gets everyone laughing, sharing, and connecting every time you play.
Use your actual service and paths. The archive filename in the example is only a local filename; obtain the archive from the official download area. If your existing data directory is inside the old application directory, move it outside before the mv or deletion step. Never run a recursive delete against a directory until you have confirmed that it contains no worlds or player data.
Launch with an explicit data path
A direct launch has the documented form:
dotnet /srv/vintagestory/server/VintagestoryServer.dll --dataPath /srv/vintagestory/data
In a systemd service, place the equivalent command in ExecStart, preserve the service user and permissions, and then reload the unit if you changed its file. Ensure that the service user can read the new application files and read/write the data directory. A permissions failure can look like a missing-world problem when the server simply cannot open its save.
Check the Linux service after replacement
- Start the service and follow its log, for example with
journalctl -u vintagestory -fif that is the unit name you use. - Confirm that the command line includes the intended
--dataPath. - Check that the process is listening on port 42420 and that the host firewall still permits both TCP and UDP traffic.
- Connect locally before testing the public address. This separates application or mod errors from router, VPN, and port-forwarding problems.
Updating an ARM64 server
The dedicated-server guide describes an ARM installation script that downloads the current server files and states that running the script again updates the installation to the latest version. If you use that method, stop the server first, back up the data directory, and rerun the same script rather than layering files manually over a running installation.
ARM64 support is labeled experimental. After an update, check that the .NET runtime, operating-system architecture, native dependencies, and every mod you use are supported on that exact machine. A successful script run proves that files were downloaded; it does not prove that a particular mod or world will load correctly. Keep the previous application payload and data backup until you have completed the same administrator and player tests used on other platforms.
Rank #4
- In Prey, you awaken aboard Talos I, a space station orbiting the moon in the year 2032.
- You are the key subject of an experiment meant to alter humanity forever - but things have gone terribly wrong.
- The space station has been overrun by hostile aliens and you are now being hunted.
Mods, clients, and version matching
Clients and servers must run matching Vintage Story game versions. A player on a different game version may be refused immediately, or may connect and encounter inconsistent behavior depending on the change. Have players update their clients before you reopen the server.
The official troubleshooting guidance recommends updating mods alongside a game update because outdated third-party code can cause failures. Treat the mod directory as part of the compatibility check, not as an afterthought.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Mod category | Update decision | What to test |
|---|---|---|
| Server-side | Update or remove it on the server when the author does not support the target game version. | Server startup, world loading, commands, and a normal player join. |
| Universal | Install the compatible version on both server and every client that needs it. | Client launch, join handshake, and any blocks or items supplied by the mod. |
| Client-side | Usually does not belong on the dedicated server, but clients may still need a matching release. | Client startup and connection to the updated server. |
Check dependencies in the order the mod author specifies. An asset, block, item, or dependency error in the startup log is often a compatibility problem rather than a damaged world. Temporarily moving one suspect mod out of the active directory is a useful diagnostic, provided you do it with the server stopped and preserve the original copy for rollback.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to verify an update before declaring success
Read the startup log
Allow the server to finish its normal startup sequence. Pay attention to warnings about migrations, missing assets, duplicate files, unresolved dependencies, permissions, or a data path that differs from your recorded path. Do not treat a process that stays running as proof of a healthy world; a server can start while a required mod has failed to load.
Test administrator and ordinary-player access
Join with an administrator account and inspect several known areas of the world. Check inventories, player locations, claims, permissions, and any modded blocks or machines that are important to your community. Then connect with a normal player account to verify that permissions and authentication survived the update.
Best Value
- 3-Piece Premium Metal Puzzle Set for Adults 15+: This curated bundle has 3 unique vintage metal disentanglement puzzles for teens and adults craving brain challenges. Precision-cast high-strength alloy brings solid weight and smooth burr-free edges, no cheap plastic parts at all.
- Durable Anti-Rust Build for Long-Term Play & Collection：Premium electroplated vintage metal coating resists scratches, fading and rust after months of repeated twisting. The sturdy structure won’t bend or break easily, making it a long-lasting collection piece for countless play sessions.
- Boost Spatial Logic & Focus in a Screen-Free Way：This 3D IQ game trains your patience, spatial imagination and reverse thinking as you twist and explore hidden mechanisms. Gradual difficulty keeps you engaged for hours, melting work stress and keeping your mind sharp.
- Pocket-Sized Fun for Travel, Parties & Gatherings：Compact and lightweight enough to slip into your bag or jeans pocket, it lets you enjoy brain teasers on commutes, trips or family game nights. It livens up group interactions and pulls everyone away from mindless scrolling.
- Thoughtful Gift for Puzzle Lovers & Special Occasions：With clear illustrated instructions, this challenging disentanglement set is perfect for birthdays, anniversaries and holiday gifting. It’s more than a game — a fun, memorable way to share quality time with friends and partners.
Test the network from the right place
A local connection confirms that the application is reachable. An external connection confirms firewall, router forwarding, VPN, and public-address settings. The server uses TCP and UDP port 42420 according to the multiplayer guide. If you changed hosts, executable paths, or network interfaces, recheck rules that may be tied to the old process or address.
Complete one save cycle
Let the server run long enough to write a save, then stop it cleanly and start it once more if your maintenance policy allows. This catches permissions and migration issues that do not appear during the first few minutes. Keep the rollback copy until this cycle and the player tests succeed.
Troubleshooting after the update
| Symptom | Most likely checks | Recovery action |
|---|---|---|
| Clients are rejected immediately | Compare the exact client and server game versions. Confirm that required universal mods are installed in compatible versions. | Align versions, then restart the client and server. Do not restore a world backup merely for a version mismatch. |
| The server starts but reports missing assets, blocks, items, or dependencies | Review the mod list, dependency versions, and startup log. Identify the first error rather than only the final cascade. | Install the supported mod release or temporarily remove the incompatible mod with the server stopped. Restore it from the preserved copy after finding a compatible version. |
| The server appears empty or creates a new world | Check the --dataPath argument, working directory, service account, and file permissions. |
Stop the server and point it at the original persistent data directory. Do not continue playing on the new empty world if you intend to return to the existing save. |
| The process will not start | Check the .NET runtime, executable permissions, architecture, service user, and the first fatal log message. | Correct the runtime or permissions, or roll back the application files while leaving the data backup untouched. |
| Local players can join but public players cannot | Check the host firewall, router port forwarding, VPN configuration, public address, and both protocols on port 42420. | Restore the network rule for the new process or host, then retest from outside the local network. |
| The world loads but behaves incorrectly | Look for mod failures, migration warnings, changed configuration, and a server accidentally pointed at a copy of the data. | Stop cleanly, preserve logs, and roll back the application and data together if the problem cannot be isolated safely. |
Optional Linux automation
The Vintage Story Mod DB lists a community Linux shell utility named Server Updater, created April 30, 2025 and last modified June 3, 2025. Its documented workflow stages a server .tar.gz, creates rollback snapshots, preserves server.sh configuration, replaces application files, and keeps the previous payload in a review folder. It expects a replaceable server/ directory beside a persistent data/ directory.
This utility is optional community tooling, not a requirement of the official update procedure. Read its current instructions before use, confirm that its expected directory layout matches yours, and verify that its snapshots are stored somewhere with enough space. Automation cannot protect data that is incorrectly located inside the directory it replaces.
Rollback plan
Rollback is simplest when the old application directory and a dated data backup still exist. Stop the updated server, record the error log, restore the previous application payload, and point the launch command at the same persistent data directory. If the update performed a world migration, restore the matching pre-update data backup as well; do not mix a migrated save with an older application unless the version’s documentation explicitly permits it.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →After rollback, test an administrator login and a normal player connection before announcing that the previous version is back. Preserve the failed update’s logs and mod changes so you know which component needs correction before the next attempt.
Maintenance checklist for future updates
- Keep application and persistent data in separate directories.
- Record the exact server version, launch command, and data path.
- Stop the server before replacing files or editing
serverconfig.json. - Back up worlds, saves, settings, player data, and mods together.
- Check mod versions, dependencies, and client/server requirements.
- Preserve firewall and port-forwarding rules for TCP and UDP 42420.
- Read startup logs instead of assuming a running process is healthy.
- Test an administrator, a normal player, and an external connection.
- Keep rollback files until the updated world completes a save cycle.
With that separation and verification routine, a Vintage Story update becomes a controlled replacement of server software rather than a risky operation on the world itself.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
