Vintage Story Server Commands: The Owner's Reference

Vintage Story server commands are slash commands for managing access, players, roles, world settings, and the server itself. The commands below were checked against the official dedicated server version 1.22.7 on October 10, 2026; the official wiki command list is marked outdated, so use your own server’s /help before relying on an old snippet. This is a task-based owner reference, not an exhaustive list of every command.

Vintage Story is a PC game for Windows, macOS, and Linux. Each player needs their own account, and the client must match the server version; there is no console edition listed by the official system requirements. These commands belong to Vintage Story itself, not Minecraft. The game’s official mod source is ModDB, not Steam Workshop; for mod compatibility and what players receive when joining, see our Vintage Story server mods guide.

Know where Vintage Story server commands run#

Server commands begin with a forward slash. You can issue them from the dedicated server console or through the game’s in-game chat and command interface when your account has the required permission. The console is the route for an owner who cannot yet enter the world; the game interface is convenient once an authorized player is online. The console’s setup and operation are a separate topic from this command index.

For this reference, I started the official Windows server build 1.22.7 with .NET 10 in a disposable local data directory. It started on its default port and returned help text; this was a local syntax check, not a Dallas test, a public network test, or a client login test. I did not test these commands on a Game Hosting production server. Keep those limits in mind before using commands that affect players or a world.

Vintage Story servers are not Minecraft servers with a different texture pack. They use Vintage Story’s own accounts, roles, world configuration, and command forms. Don’t copy Minecraft syntax or disable account authentication to get around a join problem. If friends are still deciding how to play together, the multiplayer overview compares the available routes.

Check the syntax on your own server version first#

The most reliable first command is /help. For a particular command, ask the server for its help page:

/help
/help whitelist

Square brackets in a help line indicate optional text; don’t type the brackets themselves. Angle brackets mark a value you replace, such as a player’s name. Command availability and syntax can change, and server permissions can hide or reject actions. The official command list currently labels itself outdated and says it was last verified for version 1.15. It can point you toward a command family, but it should not overrule what your running server reports.

Use /help <command> before a command you have not used, especially before changing access or world state. If the server says “No such command found,” stop there rather than guessing at a similar name. For example, /help setspawn on the 1.22.7 server used for this guide returned no such command. The server-config help lists spawn-related subcommands under /serverconfig; that does not make /setspawn a valid standalone command.

Add players and manage the whitelist#

On a new dedicated server, the whitelist is enabled by default. To add or remove someone, or open and close the whitelist gate, the 1.22.7 help returned these forms:

/whitelist add <player> [optional reason]
/whitelist remove <player>
/whitelist on
/whitelist off

The player command also accepts a whitelist subcommand:

/player <player> whitelist [add/remove] [optional reason]

Older instructions sometimes show /player <name> whitelist on. That exact form did not match the current help output. Prefer the top-level /whitelist forms above, or ask your own server for /help player and /help whitelist after an update.

Turning the whitelist off lets unlisted accounts pass that access check; it does not disable Vintage Story account authentication. Every player still needs their own account. The official dedicated-server guide describes the default whitelist behavior, while the live server help should guide the syntax. If nobody can get in, check both whitelist status and account/version requirements before changing other settings.

Give an admin role and inspect available roles#

To grant the admin role, the short form is:

/op <playername>

The live help describes /op as shorthand for assigning the admin role. The longer form lets you name another role:

/player <player> role <role>
/role <rolename>
/list roles
/list privileges

Use an existing role name exactly as the server reports it. /role is also the entry point for role configuration commands, so it is not just a way to list players. This page does not try to document every privilege or build a custom role; a dedicated roles and privileges guide can cover that workflow separately. Give admin access only to people who need it, because the role can change more than chat or building permissions.

If you rent a server and would rather manage the owner and players with controls, Game Hosting’s Vintage Story panel supports owner admin setup, whitelist controls, player actions, and a console for server commands. Those are documented panel features; the local syntax check above did not test a production account or panel action.

Check who is online and moderate access#

Use /list with a category to inspect the server’s current lists. These forms appeared in the live help:

/list clients
/list banned
/kick <player name> [kick reason]
/ban <player name> <duration> <reason>
/unban <player name>

The help output makes both a duration and a reason part of the /ban syntax. A kick reason is optional. After an unban, the player may still need to be whitelisted and able to authenticate with the correct game version. Don’t treat an empty client list as proof that the server is unreachable; it only reports connected clients at that moment.

These commands were checked for syntax only, without a second player connected. I did not test how a specific name, duration, reason, or role behaves in a live moderation case. For a dispute or an accidental ban, check /help ban, /help unban, and the server’s current player lists before changing access. The host selection guide also explains what player controls to confirm in a panel before you choose a provider.

Change time, game mode, or world settings carefully#

The 1.22.7 help exposes commands for time, game mode, and world settings:

/time set <24 hour format or word>
/gamemode [playername] [mode]
/worldconfig [key] [value]
/worldconfigcreate ...
/serverconfig whitelistmode [on/off/default]

The exact time value, mode, setting key, and accepted value depend on what the server supports. Ask for /help time, /help gamemode, /help worldconfig, or /help serverconfig before changing one. A setting may affect everyone in the world, so record the old value and explain the change to other admins. The full world settings reference and server configuration guide cover those controls in depth.

Do not substitute /setspawn because a third-party page lists it. It was absent from the help output checked here. The server-config command family has its own spawn help, but this article does not prescribe a spawn workflow. Before changing world behavior, make sure you know which save is active and how to recover it. Vintage Story world saves use SQLite-backed .vcdbs files; a command being present is not evidence that a backup can be restored.

Save a copy or stop the server without guessing#

The server help lists commands that affect saving and lifecycle:

/autosavenow
/genbackup [filename]
/stats [compact]
/stop [exit code]

/autosavenow requests a save. The help describes /genbackup as generating a copy of the save in the Backups directory, optionally using a filename. That description does not establish how long the copy remains, whether it is intact, or whether a restore will work. Before replacing, updating, or migrating a world, verify an independent backup and the recovery path you would use. Never assume that a command called “backup” has already been tested as a restore point.

/stats provides server statistics, but the presence of that command is not a performance benchmark. /stop stops the server; it can disconnect everyone and is not a complete restart recipe. Check who is online and tell the group before stopping a live world. The dedicated save and restart articles will own those procedures; use /help stop to confirm the syntax for your current server version.

Ask the handbook before trusting an old command snippet#

The short version: use a slash command in an authorized server context, and let the running server resolve uncertainty. On the 1.22.7 build checked for this guide, whitelist, role, player, moderation, time, mode, save, and server-config help were available, but this is not an exhaustive command list. After a server update, recheck the forms you depend on with /help and the relevant command-specific help.

The official server is distributed separately from the game client, but friends still need their own Vintage Story accounts and a compatible client version. The official downloads and version API can help an owner identify a current server package; .NET 10 is required for the 1.22 server line. This reference does not explain server installation, network port forwarding, mod distribution, or world restoration. Use the official dedicated-server setup guide for installation, and avoid mixing a command index with setup steps.

The most useful habit is simple: pause at any command that changes access, world settings, or server state; read the current help, check the active world and recovery plan, then make one change at a time. If you prefer a panel, the verified Vintage Story controls on the Game Hosting page let an owner manage whitelist/player actions and send commands from the console.

Sources checked October 10, 2026

• Vintage Story server command list and dedicated-server guide
• Vintage Story system requirements, single-game account page, and stable version API
• Vintage Story ModDB and server configuration reference
• Command forms were checked with /help on an official local Windows server build 1.22.7 with .NET 10. No client join, Dallas run, public connection, production-panel action, performance benchmark, or restore was tested.