Skip to main content

World Settings

Customize your Vintage Story world with these configuration options.

World Generation

Creating a New World

World settings are defined before world creation:
  1. Stop server
  2. Delete existing /Saves/ folder
  3. Configure serverconfig.json
  4. Start server
Deleting Saves folder removes your world! Always backup first!

World Seed

{
  "WorldConfig": {
    "Seed": "12345",
    "WorldName": "myworld"
  }
}
Leave seed empty for random generation.

World Size

{
  "WorldConfig": {
    "WorldWidth": 1024000,
    "WorldHeight": 256,
    "WorldDepth": 1024000
  }
}
SettingDefaultDescription
WorldWidth1024000X-axis size
WorldHeight256Vertical height
WorldDepth1024000Z-axis size

Spawn Settings

Spawn Location

{
  "DefaultSpawnX": 0,
  "DefaultSpawnY": -1,
  "DefaultSpawnZ": 0,
  "SpawnPlayerNear": "spawnpoint"
}
SettingDescription
DefaultSpawnX/Y/ZCoordinates (-1 = auto)
SpawnPlayerNear”spawnpoint” or coordinates

Player Spawning Distance

{
  "SpawnPlayerDistance": 100,
  "SpawnPlayerFarDistance": 5000
}
Controls how far new players spawn from the spawn point.

Gameplay Customization

Difficulty Settings

Configure via world creation or mods:
AspectOptions
Hunger rateSlower/Normal/Faster
Death penaltyKeep/Lose items
Creature hostilityPassive/Normal/Aggressive
Season lengthShort/Normal/Long

Time Settings

In-game commands:
/time set day
/time set night
/time speed 1.0

World Rules

Common customizations:
/weather set clear
/worldconfig

Season Configuration

Vintage Story has dynamic seasons affecting:
  • Crop growth
  • Temperature
  • Day length
  • Weather patterns

Season Length

Configurable in world settings:
  • Short seasons: Faster progression
  • Long seasons: More realistic

World Borders

Setting Boundaries

Use mods or server settings to limit world size:
{
  "WorldConfig": {
    "WorldWidth": 20000,
    "WorldDepth": 20000
  }
}
This creates a 20km x 20km world.

Chunk Management

Chunk Unloading

{
  "ChunkUnloadDistance": 128,
  "ChunkUnloadInterval": 180
}
SettingDescription
ChunkUnloadDistanceDistance before unloading
ChunkUnloadIntervalSeconds between cleanup

Performance Tips

  • Lower ChunkUnloadDistance for less RAM use
  • Higher values keep more world loaded

World Backup & Restore

Backup Location

Worlds are stored in:
/Saves/[WorldName]/

Manual Backup

  1. Stop server
  2. Download /Saves/ folder
  3. Store safely

Restore Process

  1. Stop server
  2. Delete current /Saves/ folder
  3. Upload backup
  4. Start server

World Commands

Administrative Commands

CommandDescription
/time set <time>Set world time
/weather set <type>Change weather
/worldconfigView world settings
/saveForce world save

Time Options

/time set day
/time set night
/time set morning
/time set evening

Weather Options

/weather set clear
/weather set rain
/weather set storm

Common World Issues

World Too Large

Problem: Server lag, high RAM usage Solutions:
  • Set smaller world dimensions
  • Use world border
  • Prune distant chunks

Slow World Generation

Problem: Lag when exploring new areas Solutions:
  • Pre-generate world areas
  • Reduce view distance
  • Upgrade server RAM

Missing Structures

Problem: Expected structures not generating Causes:
  • Seed doesn’t contain structure
  • World already generated in that area
  • Mod interference

Pre-generating World

For better performance, pre-generate chunks:
  1. Use world generation mods
  2. Or manually explore key areas before opening server
  3. Reduces lag during player exploration

Migrating Worlds

To New Server

  1. Download world from old server
  2. Upload to new server’s /Saves/ folder
  3. Match server version and mods
  4. Start server

Between VS Versions

Major version updates may require world conversion or have compatibility issues.
  1. Backup original world
  2. Update server version
  3. Test thoroughly
  4. Roll back if issues

Best Practices

  1. Decide settings before start - World settings apply at creation
  2. Regular backups - Schedule automatic backups
  3. Document your seed - Save it separately
  4. Test in singleplayer - Verify settings work
  5. Communicate changes - Notify players of world resets

Next Steps