Hosting a Vintage Story Community Server: What It Needs
A Vintage Story community server needs clear roles, claim rules, compatible mods and enough memory. Compare hosting options before inviting players.
You will need
- Each player has a Vintage Story account and a supported PC
- Your group has a rough player count and exploration style in mind
- List the rules, mods and world you expect to keep
A Vintage Story community server needs more than an address: organizers should be able to explain who can join, what each staff role can change, how claims fit the rules, what mods players need and how the world can be recovered. Before inviting members, compare the host’s published resources and management tools with the way your group will explore and build. This checklist focuses on that buying decision; it does not promise a player capacity or a tested recovery result.
If you are still choosing between a rented server and running one yourself, start with our guide to renting, a home PC and a VPS. This page is for organizers who already know they want a persistent community world.
Decide what your community needs the host to handle#
Write down the jobs that have to keep working when the organizer is offline. That list helps you compare hosts by the workflow your group will actually use, instead of by a player-slot number in a product name.
| Community need | What to check before choosing |
|---|---|
| Members join while the owner is away | Whitelist controls, owner access and a way to grant staff roles |
| Settlements grow in different regions | Published memory and CPU details, plus a realistic plan to watch load |
| The group plays with mods | ModDB search, version visibility and clear client/server mod handling |
| A world already exists | Upload path, downtime required, backup process and recovery steps |
| Members are spread across countries | Host location and a way to check the route from players’ regions |
If your members are spread out, compare their real routes before settling on a region. This guide to Vintage Story server location and ping walks through a group test without promising that one city fits everyone.
Vintage Story is currently listed for 64-bit Windows 10 or newer, macOS 13 or newer, and Linux. The official requirements and purchase pages list PC versions; they do not list a console or Steam release as of October 14, 2026. Each player needs their own account from vintagestory.at, and server authentication should remain enabled. A rented host does not remove those client and account requirements.
Ask who will own billing, keep the mod list current, review reports and approve world changes. A host can provide server controls, but it cannot decide your conduct rules or settle disputes for you. If your goal is a roleplay plan rather than a host checklist, see how to run a Vintage Story RP server.
Separate the whitelist from staff privileges#
The whitelist decides who may enter; a role decides what an admitted player can do. Treat them as two controls. Adding someone to a moderator group should not automatically mean they need every administrative privilege, and a trusted builder may not need permission to change server settings.
The current dedicated-server guide describes server roles and permissions, while the sample configuration names the default player role suplayer. Roles can include different privileges and land-claim allowances. That sample’s default is not a policy recommendation for every community, and it was last verified against 1.22.0. Check the current in-game Command Handbook or /help on your server version before copying command syntax from older wiki pages.
Before opening applications, decide who can invite players, moderate chat, manage the world and change settings. Give each responsibility to a named person, then test the join and permission flow with a non-owner account. If a host provides an owner whitelist, admin access and a player roster, verify that those controls are visible to the account that will run the community. Game Hosting’s Vintage Story panel includes owner access, a whitelist control and player management; its role presets cover suplayer, limitedsuplayer and suvisitor. Advanced role and privilege fields still need to be reviewed in the server files.
Keep the Vintage Story community server join path simple for members: one address, one version expectation and a clear place to request access. Do not disable account validation to bypass an authentication problem; check the game’s service status and retry when it is available.
Size the server around memory and exploration#
Use the official estimate as an initial planning point, then leave room to observe the world you actually run. The dedicated-server guide suggests roughly 1 GB plus 300 MB per player and 4 threads for a normal world where players are spread out. It calls these conservative estimates, not a benchmark or a guaranteed population figure. Distant bases, exploration, mods and world activity change the load.
| Published plan detail | What it tells you | What it does not prove |
|---|---|---|
| Memory in GB | The amount of memory assigned or guaranteed under the plan’s terms | How many players a particular modded world will support |
| CPU model and threads | Hardware and thread allocation to compare between offers | Tick rate or performance under your community’s workload |
| Player recommendation | A planning hint from that host | A technical cap or tested capacity |
| Location | Where the service is hosted | The latency every member will see |
Our separate Vintage Story RAM guide explains the estimate’s limits and why bases far apart can change memory needs. Do not translate a simple formula into “this plan supports N players.” Ask whether resources are dedicated or shared, what happens if a world approaches its limit, and whether the host exposes useful usage information. If an offer lists slots but hides memory and CPU, you cannot compare its resource allowance directly with a plan that publishes those numbers.
Match land claims and moderation to your rules#
Claims can protect builds; they do not replace a moderation plan. Decide whether players may claim private homes, shared farms, roads or community buildings, and how staff should handle abandoned areas. Then check whether the host lets you configure the game’s relevant role and claim settings or edit the underlying files.
Vintage Story roles can carry different claim allowances, and the sample suplayer role allows up to eight chunks. That is a sample setting, not a safe limit for your community. You may want smaller allowances for new arrivals and separate treatment for public projects. Explain the rule before players start building so that a later adjustment does not surprise them.
For grief reports, decide where players report a problem, who reviews it and what evidence should be preserved. The AntiAbuse setting and block-event logging have distinct purposes; block logging is off by default in the sample configuration. Official 1.22.6 patch notes describe block-burst autobanning when anti-abuse is enabled and a log-based way to restore certain deleted blocks from server-build.log. That is a narrow recovery feature, not a complete world rollback or a substitute for a separate world backup. If your rules include roleplay, decide how staff handle reports and disputes as part of your community setup; do not promise a host can undo every incident.
Check ModDB and version handling before you install mods#
Vintage Story’s community mods come through ModDB, not Steam Workshop. A mod’s side determines what your group must install: the official server guide says server-side and universal mods can be offered to clients when they join, while client-side mods are each player’s responsibility. Check the mod’s release page for its supported game version and dependencies, then confirm your host’s panel supports the installation method you plan to use.
Before changing a live community server:
- Record the server and client version the group is using.
- Review each ModDB release’s version tags, side and dependencies.
- Back up the world and mod files before updating or removing anything.
- Test the changed set on a copy or quiet maintenance window, then tell players what they need to update.
The current stable release is 1.22.7, but a version number alone does not prove that an arbitrary mod combination works. Keep the server version visible, and agree on how much notice you will give members before changing it. Our Vintage Story server mod guide covers the server/client distinction and ModDB workflow in more detail. Game Hosting’s Vintage Story panel includes a ModDB search and version controls, but that is not a promise that every mod or combination is compatible.
Compare hosting offers by terms you can verify#
We recommend Game Hosting’s Vintage Story plans to organizers who want memory and CPU details, owner controls, ModDB and version tools, and three included backup slots. Its current plans list 4, 8 or 12 GB of guaranteed RAM, Ryzen 9 9900X hardware with four threads, and a Dallas product location. The page’s 20-player recommendation is a planning suggestion, not a tested cap. The web file manager does not include SFTP, so check upload needs if you expect frequent large world or mod transfers.
| Host | Published details useful to a community | Check before choosing |
|---|---|---|
| Game Hosting | 4/8/12 GB RAM plans, Ryzen 9 9900X with 4 threads, 3 backup slots, owner whitelist/admin controls, ModDB and version tools; Dallas location | Dallas may not suit members elsewhere; no SFTP; recommendations are not tested capacity |
| Indifferent Broccoli | 4/8/16/32 player-count tiers, “uncapped RAM,” multiple named regions, full file access, Discord /status and /restart functions |
Numeric RAM per tier is not published on its current product page; confirm the exact region and terms |
These are features stated on the providers’ pages checked October 14, 2026, not a benchmark or a restore test. Indifferent Broccoli’s broader location choice and full file access may fit a group that needs those things. Its player-count tiers and uncapped-RAM wording do not map to a published GB figure, so compare the offer directly with the workload and terms you need. Our general host selection guide explains more comparison checks. The team behind Game Hosting publishes this article; the recommendation rests on the listed details above, not on a claim that we tested every provider.
Keep the world recoverable before changes#
Ask the provider what is backed up, how many copies are retained, where they are stored, and how you can inspect or restore one. A label like “backup included” does not tell you whether the copy includes the world, server configuration and mods, or what happens to newer changes during a restore.
Before an update, mod change, world upload or restore, make a fresh backup and verify that it completed. Keep a separate copy if the world matters to the community. Read the restore consequences first: a restore can replace current progress, and an upload can point the server at a different save. Vintage Story worlds use SQLite-backed save files; never experiment on the only copy. The server guide covers the self-hosted runtime and file layout, while a host should explain its own backup process and limits.
Game Hosting includes three backup slots with scheduling, restore, download and locking controls. This describes the available product features, not a restore we ran for this article. For any provider, ask how to confirm a backup exists and what data the restore replaces before relying on it for an incident.
Make the invite-ready decision#
Choose a host only after you can answer these questions in plain language:
- Can every member use a supported PC platform, and does each person have their own game account?
- Who may join, and which staff members need which in-game powers?
- How will claims protect homes without blocking shared areas?
- What memory, CPU, location and backup terms does the plan actually publish?
- How will you check ModDB release versions, client requirements and dependencies?
- Who tests a world or mod change, and how will the group be notified?
- What does restoring a backup replace, and how will you preserve a copy first?
If the answers point to a persistent, managed world, compare the documented controls and recovery process alongside resources. Game Hosting is a fit when its stated memory, CPU, panel tools and Dallas location suit your group; look at alternatives if your members need a different region or file-transfer workflow. Once the host is chosen, use the separate roleplay setup guide to plan the community’s play rules, not as a substitute for checking what the provider actually offers.
Sources and method#
We checked official Vintage Story documentation and product pages on October 14, 2026. The main references are the system requirements, dedicated-server guide, server configuration reference, ModDB, 1.22.6 server safety notes, and the providers’ current plan pages. We compared published features; we did not benchmark servers, test a player join, or restore a world from either provider.
Quick answers
How many players can a Vintage Story community server support?
There is no fixed player count that applies to every world. The official 1 GB plus 300 MB per player starting estimate is rough guidance, not a capacity test or a plan guarantee.
How should we give staff access?
Keep the whitelist and game role separate: allow a person to join first, then grant only the privileges their job needs. Check the current command handbook for exact syntax.
Are land claims enough to stop griefing?
No. Claims protect defined areas; community rules, reports and moderation still matter, and logging must be enabled before an incident if you need an audit trail.
Do players need to install mods for a server?
It depends on each mod. Server-side and universal mods can be offered to clients at join; client-side mods must be installed by each player, and versions and dependencies must fit the server.
What should we compare when choosing a host?
Compare published memory and CPU, version and ModDB handling, backup recovery, access controls, support and the regions your members use.