Configure Land Claiming on a Vintage Story Server

This guide walks you through setting up land claiming on your Vintage Story server, so players can protect their builds from griefing and unwanted edits. You’ll learn how to enable the protection system, define claim areas, and manage permissions—whether you run a small private server or a larger community. No mods are required; everything is built into the game’s server configuration.

What You’ll Need

• Access to your server’s configuration files (usually in the VintagestoryServer folder or via your hosting panel’s file manager).
• Server console or in-game admin commands (you must be an admin or have the server role).
• Basic familiarity with editing JSON files (for advanced settings).

Step-by-Step

1. Stop the server (if it’s running) to safely edit configuration files. You can do this from your hosting panel or by sending the stop command in the console.
2. Locate the main config file: Navigate to your server’s root folder and open VintagestoryServerConfig.json (or serverconfig.json depending on version). This file contains global server settings.
3. Enable land claiming: Look for the "LandClaiming" section. If it doesn’t exist, add it. Set "Enabled": true. Keep the rest of the defaults unless you have specific needs. Save the file.
4. Start the server and wait for it to fully load. The land claiming system is now active.
5. Assign the claim tool: In-game, as an admin, run the command /grant @p command:claim to give yourself the claim command. For other players, replace @p with their username or use @a for all players (not recommended for public servers).
6. Create a claim: Stand in the first corner of the area you want to protect. Type /claim create to set the first point. Then walk to the opposite corner and type /claim create again. The claim is now created as a rectangular prism (full height from bedrock to sky).
7. Manage claims: Use /claim list to see all claims, /claim delete to remove the claim you’re standing in, and /claim info to view details of the current claim.
8. Set permissions: By default, only the claim owner can build. To allow friends, use /claim add <playername> while standing in the claim. To remove, use /claim remove <playername>.
9. Adjust claim size limits (optional): In the config file, under LandClaiming, you can set MaxClaimsPerPlayer, MaxClaimArea (in blocks), and MinClaimArea. For example, "MaxClaimArea": 10000 allows a 100×100 block area. Restart the server after changes.
10. Test the claim: Have a non-owner player try to break a block inside the claim. They should receive a message that the area is protected.

Common Mistakes

• Forgetting to grant the command: Even with claiming enabled, players without the claim command cannot create claims. Always grant it via /grant.
• Creating claims that overlap: Claims cannot overlap. If you try to create a second claim that intersects an existing one, the game will reject it. Plan your areas carefully.
• Misunderstanding claim height: Claims extend from bedrock to the sky, so you cannot protect just a basement—it protects the entire column.
• Editing the wrong config file: Some server hosts have multiple config files. Make sure you edit the main one, not the client-side or world-specific config.
• Not restarting after config changes: Changes to the JSON file require a server restart to take effect.

Tips

• Use /claim list regularly to keep track of claims, especially on public servers.
• Set a reasonable MaxClaimArea to prevent players from claiming huge chunks of the map. A common default is 10000 blocks (100×100).
• Encourage players to claim only what they need. You can also set MaxClaimsPerPlayer to 1 to keep things tidy.
• For temporary protection during events, you can use /claim temp <minutes> to create a claim that expires.
• If you want to allow building for everyone in a claim (e.g., a community farm), use /claim add @a to add all players.

Troubleshooting

• Claim command not working: Check that you have granted the command correctly. Type /grant list to see your permissions. Re-grant if necessary.
• Claims not saving after restart: Ensure the server shuts down gracefully (not killed). Claims are stored in the world save, so a force-stop can corrupt them. Always use the stop command.
• Players can still break blocks in claims: Verify that the claim was created properly with /claim info. Also check if the player is the owner or has been added. If using a mod that bypasses protection, remove it.
• Config changes not applying: Make sure you edited the correct file and restarted the server. Some hosting panels cache configs—try a full server restart (not just world reload).
• Claims cannot be created because of “insufficient area”: This usually means your claim is too small. Check MinClaimArea in the config and increase it if needed.

Frequently Asked Questions

Do I need a mod to enable land claiming?

No. Land claiming is a built-in feature in Vintage Story. You only need to enable it in the server config.

Can I claim an area that already has another player’s build?

Yes, but only if that area is not already claimed. If it is claimed, you must ask the owner to add you or delete the claim.

How do I make a claim that only I can build in, but others can use doors and chests?

By default, claims block all interactions. To allow specific interactions, you’d need to use a mod like Block Interaction or adjust the server’s group permissions. The base game only supports full protection or full access.

What happens if I delete a claim?

The land becomes unprotected immediately. Any blocks placed by the owner remain, but anyone can now modify them.

Can I transfer a claim to another player?

Currently, there is no built-in transfer command. The owner must delete the claim, and the new owner must recreate it.

Is there a limit to how many claims I can make?

Yes, the default is 5 claims per player. You can change this in the config under MaxClaimsPerPlayer.

Related

• Ollama Performance Tuning for Faster Local LLMs
• Evaluate AI-Generated Code Fixes Before Merging
• AI-Generated Database Queries: Read-Only Access