Skip to content

Configuration

Jump to bottom
DEVKruidenier edited this page Nov 11, 2026 · 25 revisions

Configuration

plugins/LandWard/config.yml contains all LandWard settings. Each setting has an English explanation in the file itself.

plugin-version at the top is informational only. LandWard sets it to the installed JAR version automatically; do not edit it.

Safe updates: Your changed values are kept when LandWard updates. New settings are added automatically; check the file after a major update.

Language and storage

language:
  default: en_US
  use-client-locale: true

storage:
  type: sqlite

Language packs live in plugins/LandWard/lang/. LandWard includes English, Dutch, German, French, Spanish and several other common languages. With use-client-locale: true, players see a matching installed language when available; otherwise LandWard uses the default language above.

See Storage before changing the backend.

Claims and worlds

claims:
  require-adjacent-chunks: true
  maximum-lands-per-player: 1
  maximum-chunks-per-land: 25 # -1 means unlimited
  # LandWard is active everywhere except worlds listed here.
  disabled-worlds:
    - myworld

LandWard is active in every world by default. List only worlds where it should be off, such as creative or minigame worlds. myworld is only an example; you can remove it.

Payments and rename cost

payments:
  mode: free # free, experience or vault
  experience-points-per-chunk: 150
  vault-money-per-chunk: 100.0

rename:
  experience-level-cost: 0

teleportation:
  player-land-delay-seconds: 2
  • free charges nothing.
  • experience charges total experience points for each newly claimed chunk.
  • vault uses Vault’s active economy provider, such as EssentialsX Economy.
  • experience-level-cost: 0 keeps renaming free; a positive value charges that many XP levels after a successful anvil confirmation.
  • player-land-delay-seconds is the wait before an owner teleports to the first claimed chunk from the land menu. Set it to 0 for an immediate teleport.

Player-claim member defaults

player-claims:
  member-rights:
    build: true
    containers: true
    entities: true

These values are copied to a player land when it is created. The owner can change the land's defaults in Settings and can then customise build, container and protected-entity access for any individual member. Existing lands and members keep their saved choices when this section changes. Changing a land's default affects members added afterwards and never replaces an existing member's individual choice.

Admin claims

admin-claims:
  # Keep default-name: '' to use the name from the selected LandWard language.
  # To set a custom name, use for example: default-name: Spawn
  default-name: ''
  member-rights:
    build: true
    containers: true
    entities: true
  protection:
    allow-build: false
    allow-entities: false
    allow-pvp: false
    allow-hostile-mob-kills: false
    allow-passive-mob-kills: true
    allow-containers: false
    allow-doors: false
    allow-interactions: false
    allow-hostile-mob-spawns: false

Admin claims are purple server-owned Safe Zones, for example at spawn. Manage them through the separate Admin claims map. Public protection can be changed in ClaimAdmin. member-rights supplies the initial rights for members of a new Safe Zone; administrators can customise each trusted member separately. Changing these member-right defaults does not overwrite existing members' saved rights. The public protection switches apply to all Safe Zones, including existing ones, when the configuration is reloaded or changed through ClaimAdmin.

Integrations and updates

The remaining sections configure optional integrations, metrics and release checks. Turning on a setting does not install another plugin; LandWard simply uses that integration when the other plugin is installed.

See Integrations for what each bridge does.

updates:
  enabled: true
  # Login notices are available from LandWard 1.0.2.0.
  notify-on-join: true
  maximum-download-megabytes: 32

When an official release is newer, /claim update can download a verified JAR to plugins/LandWard/updates/. It is deliberately staged only: Paper does not provide a safe live replacement for a running plugin's classes, listeners, integrations and open storage connections. Stop the server, replace the plugin JAR with the staged file, then start the server normally.

From 1.0.2.0, with notify-on-join: true, operators and players with landward.pladmin see a colored update summary after joining when a newer official release exists. Set it to false to disable login notices while keeping update checks and the console summary. Setting enabled: false disables release checks entirely.

Next: Storage · Integrations · Installation

Clone this wiki locally