Menu
 

Vintage Story /worldconfig: Commands, Settings and Values

Vintage Story /worldconfig: Commands and Settings

Current stable build: 1.22.7 on Supercraft. World-creation menu data checked October 13, 2026.

Use this reference to read or change built-in world settings with /worldconfig, choose values before starting a world, and decide what belongs in serverconfig.json. The table below adds the exact presets shown in the Vintage Story 1.22.7 world-creation menu.

Syntax

  • /worldconfig name: read the current value.
  • /worldconfig name value: set it. The value is written into the save, and the server always answers Ok, value ... set. Restart game world or server to apply changes. World-generation changes then affect only newly generated chunks.
  • /worldconfigcreate datatype name value: create a key that has no built-in default. Datatypes: float, double, int, string, bool. Mostly used by mods that read their settings from worldconfig.

worldconfig vs serverconfig.json

The WorldConfiguration block inside WorldConfig in serverconfig.json is read only when a new world is created; the server copies it into the new save. After that the world keeps its own copy, so editing serverconfig.json no longer changes it. Use /worldconfig to read or change a setting on an existing world. Some generation changes affect only chunks created after the change, and some settings are exposed only on the world-creation screen. Check the behavior for the specific key instead of assuming every setting works the same way. Server-level settings such as ports, whitelist and max players are covered in the serverconfig.json guide.

Selected built-in settings

Spawn and death:

  • gameMode: survival (default) or creative.
  • deathPunishment: drop (default) or keep. This controls whether inventory is dropped on death.
  • spawnRadius: scatter of fresh spawns in blocks (default 50). Lower values keep new spawns closer to the map center.
  • graceTimer: in-game days before hostile creatures spawn (default 0). For a slower start, choose 5 days when creating the world.
  • playerlives: lives before permanent death; -1 means infinite lives. This can set a life limit for a challenge world.

Difficulty:

  • creatureHostility: aggressive (default), passive, or off. The shipped setting description says passive creatures attack only when provoked; off makes creatures never fight back.
  • playerHealthPoints: base health, default 15.
  • playerHungerSpeed: multiplier, default 1. The creation menu offers presets from 0.25 to 2. Values below 1 slow hunger; values above 1 speed it up. See food preservation when adjusting the food pace.

Worldgen multipliers (new chunks only):

  • globalTemperature: default 1. Creation-menu presets below 1 trend colder and presets above 1 warmer.
  • globalPrecipitation: default 1. Its creation-menu presets pair with temperature to define climate bands.
  • seasons: enabled (default) or pinned to a single season (spring, summer, fall, winter).

The world-generation settings shape newly generated chunks. Changing temperature or precipitation after exploration has started can leave different climate patterns in old and new areas. Decide the target before launch if you want consistent terrain. The Vintage Story world generator lets you preview temperature, precipitation and world-generation combinations before starting a server.

The shipped build data confirms defaults and creation-menu presets, but it does not establish every value accepted by /worldconfig after world creation. The linked Vintage Story Wiki marks its command-range list outdated, so full command bounds remain unverified here. Use the table below for build-checked menu choices and read the server response when setting a value.

World-creation menu presets in version 1.22.7

These are the defaults and dropdown choices read from the shipped build for the settings this page discusses. They are menu presets, not a complete list of values accepted by each /worldconfig command. The Vintage Story Wiki world-configuration page documents command syntax and ranges, but currently marks itself outdated.

Creation menu only records the setting's built-in world-creation screen flag. It does not say whether a command can change the value after a world starts. Changes to the temperature and precipitation parameters affect newly generated chunks.

SettingDefaultMenu choicesCreation menu only
gameModesurvivalsurvival, creativeNo
deathPunishmentdropdrop, keepNo
spawnRadius5010000, 5000, 2500, 1000, 500, 250, 100, 50, 25, 0No
graceTimer010, 5, 4, 3, 2, 1, 0Yes
playerlives-11, 2, 3, 4, 5, 10, 20, -1No
creatureHostilityaggressiveaggressive, passive, offNo
playerHealthPoints155, 10, 15, 20, 25, 30, 35No
playerHungerSpeed12, 1.5, 1.25, 1, 0.75, 0.5, 0.25No
globalTemperature14, 2, 1.5, 1, 0.75, 0.5, 0.25Yes
globalPrecipitation14, 2, 1.5, 1, 0.5, 0.25, 0.1Yes
seasonsenabledenabled, spring, summer, fall, winterNo
temporalStormssometimesoff, veryrare, rare, sometimes, often, veryoftenNo
landcover0.9750, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.95, 0.975, 1Yes

Example server presets

  • Gentler co-op example: graceTimer 5, deathPunishment keep, playerHungerSpeed 0.75, spawnRadius 25.
  • Default-plus example: keep the defaults except graceTimer 2 for two days before hostile creatures spawn.
  • Hardcore event example: playerlives 3, deathPunishment drop, playerHungerSpeed 1.25, creatureHostility aggressive.

Operational notes

  • Changes are admin-gated: /worldconfig and /worldconfigcreate require the controlserver privilege, which of the stock roles only admin has, so see the admin command reference for the role and privilege setup and for everything beyond worldconfig.
  • Restart after a change. Every /worldconfig set asks for a world or server restart before it applies.
  • Mods extend this surface. Modded servers accumulate worldconfig keys (set via /worldconfigcreate) that vanilla never documents, when a mod's behavior seems unconfigurable, check its Mod DB page for worldconfig lines before editing JSON by hand.

Setting up a fresh world with the climate you want? Host a Vintage Story server with Supercraft, console access for worldconfig and daily backups.

Looking for managed Vintage Story server hosting? Supercraft runs Vintage Story dedicated servers with daily backups, instant setup, and 4 region options.

Frequently asked questions

How do I change worldconfig in Vintage Story?

As an admin, run /worldconfig name to read a value and /worldconfig name value to set it. For example, /worldconfig graceTimer 5 sets a five-day grace timer. Every change needs a world or server restart, and world-generation changes affect only newly generated chunks. The creation-menu table above shows preset choices, not every value accepted by a command. For a setting with no built-in key, /worldconfigcreate datatype name value creates one; datatypes are float, double, int, string, and bool.

What is the difference between worldconfig and serverconfig.json in Vintage Story?

serverconfig.json supplies the world settings only when a new world is created; the server copies them into the save. On an existing world, /worldconfig reads and changes the copy in the save, and a world or server restart applies it. World-generation changes affect only chunks created after the change, so editing a value does not regenerate terrain that already exists.

What are the most useful worldconfig settings for a server?

Start with the setting that matches the goal: graceTimer changes the initial creature grace period; deathPunishment selects drop or keep; creatureHostility selects aggressive, passive, or off; playerHealthPoints and playerHungerSpeed adjust survival pressure; playerlives sets a life limit; and globalTemperature and globalPrecipitation shape world generation. The table above lists the current build's defaults and creation-menu presets for these keys.

How do I make a Vintage Story server easier for new players?

One gentler setup is graceTimer 5, deathPunishment keep, playerHungerSpeed 0.75, and creatureHostility passive. These are example settings, not a community-wide standard. Check each key's behavior before applying it to an existing world.

Do temperature and precipitation worldconfig changes affect existing chunks?

globalTemperature and globalPrecipitation affect world generation. Already-generated chunks keep their existing climate while new chunks use the changed values. Set your target before launch if you want a consistent world, and preview it in the Vintage Story world generator.

What does worldconfigcreate do in Vintage Story?

It creates a worldconfig entry that does not exist as a built-in key: /worldconfigcreate datatype name value, with datatypes float, double, int, string, and bool. Its main audience is modded servers: many mods read their configuration from worldconfig keys and document a worldconfigcreate line to set them.

Launch a Vintage Story server with this setup

Pick a preset and your new server boots preconfigured - rates, rules and mods already dialed in. Change anything later in the panel.

Browse all Vintage Story recipes →

Vintage Story Creative Builder

Peaceful builder preset: creative game-mode allowed, passive creatures, no temporal storms, doubled harvest, …

Vintage Story Hardcore Survival

High-stress survival preset: aggressive creatures, frequent temporal storms, slower harvest acceleration, per…

Tired of fighting this issue every patch?

Run a managed Vintage Story server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Vintage Story hosting plans →
Top