Vacer.de
MinecraftMMORPG

Camps

What are camps, and how do they work?

Camp System Documentation

The Camp System allows players to claim and manage chunks of land in Minecraft, creating protected areas where they can build, store items, and collaborate with trusted players.

Getting Started

Camps Menu

Creating Your First Camp

To create a camp, you need to be in an allowed world and standing in an unclaimed chunk.

Players can only own one camp at a time. Each camp starts with a single chunk that can be expanded later.

/camp create

or use the shorter alias:

/claim

When you create a camp:

  • The chunk you're standing in becomes claimed
  • A spawn point is automatically set at your location
  • Your camp is given a default name: [Your Name]'s Camp
  • Visual particle borders appear for 30 seconds showing your claim boundaries

Restrictions

You cannot create a camp:

  • In disallowed worlds
  • In regions containing "area" or "arena"
  • In chunks already claimed by another player

Core Commands

Camp Overview

Open the main camp management GUI:

/camp

This displays:

  • Your current chunk count
  • Bank balance
  • Quick access to spawn teleportation

Expanding Your Camp

Stand in an adjacent unclaimed chunk and run:

/camp expand

Expansion Rules:

  • New chunks must be adjacent (share an edge) with your existing claim
  • The first 4 chunks are free
  • Starting from the 5th chunk, each costs money (base $150, increasing by 1.5× per chunk)

Teleportation

Teleport to your camp's spawn point:

/camp spawn

Teleport to a specific camp you have access to:

/camp spawn <camp-name>

Viewing Borders

Display your camp's chunk boundaries for 30 seconds:

/camp borders

Particle borders will outline all chunks in your claim, showing only the outer perimeter.

Trust & Permissions

Trusting Players

Allow another player to access your camp:

/camp trust <player>

Trusted players can:

  • Teleport to your camp spawn
  • Access the camp bank (deposit/withdraw)
  • Interact based on your flag settings

Managing Trusted Players

Open the trusted players management GUI:

/camp members

From this interface you can:

  • View all trusted players
  • Right-click player heads to remove trust
  • Use /camp trust <player> to add more players

Camp Flags

Flags control what actions are allowed in your camp. Access the flags menu:

/camp flags

Available Flags

FlagDescription
PvPEnable/disable player vs player combat
BuildAllow/prevent block placement
BreakAllow/prevent block breaking
InteractControl interaction with blocks (chests, doors, etc.)
UseControl item usage within the camp

Only camp owners can modify flags. Changes apply to all non-trusted players in your camp.

Bank System

Each camp has a shared bank account accessible by the owner and trusted players.

Opening the Bank

/camp bank

Or open a specific camp's bank:

/camp bank <camp-name>

Depositing Money

  1. Open the bank GUI
  2. Click Deposit Money
  3. Use the + button to add increments
  4. Right-click the wool item to switch increment sizes (10, 50, 100, 500, 1k, 10k, 100k)
  5. Click the name tag to confirm the deposit

Withdrawing Money

  1. Open the bank GUI
  2. Click Withdraw Money
  3. Use the + button to add increments
  4. Right-click the wool item to switch increment sizes
  5. Click the name tag to confirm the withdrawal

Withdrawals require sufficient balance in the camp bank. Only the camp owner and trusted players can withdraw.

Camp Settings

Access camp settings:

/camp settings

Renaming Your Camp

  1. Click Set Camp Name in the settings GUI
  2. Type the new name in chat (max 20 characters)
  3. Type cancel to abort the renaming process

Setting Spawn Point

  1. Stand at your desired spawn location
  2. Click Set Camp Spawn in the settings GUI
  3. The spawn point is immediately updated

Abandoning Your Camp

Warning: This action is irreversible! All claimed chunks, bank balance, and settings will be permanently deleted.

  1. Open settings
  2. Click Abandon Camp
  3. Your camp is immediately deleted

Visual Indicators

Chunk Entry Notifications

When entering a camp chunk, you'll see:

Your Own Camp:

  • Title: "You entered your Camp!"
  • Boss bar: "Your Camp: [Camp Name]"

Another Player's Camp:

  • Title: "Camp entered: [Camp Name]"
  • Boss bar: "Camp: [Camp Name]"

Wilderness:

  • Title: "Entered Wilderness"
  • Subtitle: "Explore and survive!"
  • Boss bar is removed

Particle Borders

  • Appear automatically for 30 seconds when creating or expanding
  • Can be manually triggered with /camp borders
  • Only show the outer perimeter of multi-chunk claims
  • Displayed at your current Y-level

Admin Commands

Requires: camp.admin permission

Reset All Camps

Permanently delete all camps on the server:

/camp reset

Reload Configuration

Reload the camp system scripts:

/camp reload

Permissions

PermissionDescription
camp.adminAccess to admin commands (reset, reload)
vacer.camp.max_chunk.*Unlimited chunk claims
vacer.camp.max_chunk.<number>Specific chunk limit (e.g., vacer.camp.max_chunk.10)

If no permission is set, players default to a maximum of 1 chunk.

Tab Completion

The /camp command provides context-aware tab completion:

  • Base commands are always available: create
  • Owner-only commands appear when you own a camp: expand, borders, members, settings, trust, flags
  • Access-based commands appear for owned or trusted camps: spawn, bank
  • Camp names auto-complete for spawn and bank subcommands
  • Player names auto-complete for the trust subcommand

Technical Details

Chunk Storage

  • Each camp stores a list of claimed chunks
  • Chunks are identified by their coordinates
  • The system prevents overlapping claims

Data Structure

Camps store the following data:

  • Owner UUID: The player who created the camp
  • Trusted Players: List of player UUIDs with access
  • Chunks: List of claimed chunk objects
  • Spawn Location: Teleport destination
  • Flags: Boolean settings for camp behavior
  • Bank Balance: Shared money pool
  • Settings: Camp name and configuration

Adjacent Chunk Detection

Expansion requires new chunks to share an edge with existing claims. Diagonal connections are not considered adjacent.