Modifying a Vintage Story server's version, whether to apply an update or transition to a different release, is essential for server stability and community management. Upgrading to the newest release ensures compatibility with updated player clients and introduces fresh content. Selecting an older stable build or an experimental pre-release allows communities to customize their gameplay or test upcoming features.
| Guide |
|---|
| Update Server |
| Change Versions |
Note: Make backups locally to save any necessary files.
How to Update a Vintage Story Server
1. Log in to the BisectHosting Starbase panel.
2. Stop the server.
3. Ensure the Dotnet Version matches the latest version.
4. Go to the Startup tab.
5. From the Release Type dropdown, choose Stable.
6. In the Release Version field, enter latest.
7. Ensure Auto Update is set to Enabled.
8. Start the server.
How to Change Versions on a Vintage Story Server
1. Log in to the BisectHosting Starbase panel.
2. Stop the server.
3. Go to the Startup tab.
4. From the Release Type dropdown, choose a type.
-
Stable- Latest recommended release build -
Unstable- Upcoming pre-release build -
Pre- Early experimental build
5. On the Release Version field, enter the designated version.
-
Stable Type - Enter a stable version from here.
1.18.8is the oldest version allowed for Dotnet Version 7. - Unstable Type - Check the latest news here.
6. If the release type is Pre, open the Vintage Story Info page. If not, skip to step 11.
7. From the desired version, copy the Linux 64bit - Server Only download link.
8. Return to the BisectHosting Starbase panel.
9. On the Release Version field, paste the link from step 7.
10. Omit everything except for the version numbers. Ex: 1.20.0-pre.13
11. Ensure Auto Update is set to Enabled.
12. Go to the Home tab.
13. From the Dotnet Version dropdown, choose the required version.
-
Dotnet 7 - Vintage Story
1.18.8-1.20.x -
Dotnet 8 - Vintage Story
1.21.x -
Dotnet 10 - Vintage Story
1.22.x
14. Start the server.