Skip to content
RitomasssCommunity
Modular territory platform

NexaClaims Documentation

NexaClaims protects survival worlds with chunk claims, selection regions, member roles, vaults, warps, economy, nations and land wars. Every large subsystem is module-gated, YAML-configurable and exposed through safe admin diagnostics.

Paper 1.21.xJava 21 target
SQLite / SQLYAML and JDBC paths
Claims + NationsProtection to diplomacy
API readyBukkit service + events

Installation#

Install the core first, then enable optional integrations only after the claim flow is verified.

NexaClaims is Paper-first. Vault, PlaceholderAPI, LuckPerms, map plugins, Bedrock bridges and economy/shop hooks are soft integrations.
Place the jarCopy NexaClaims-x.y.z.jar into plugins/ on a Paper 1.21.x server.
Generate defaultsStart once and let the plugin create config.yml, messages.yml, modules.yml, integrations.yml, templates.yml and menu.yml.
Set the licenseReplace license-key: "LICENSE" in config.yml. The configured fail action decides whether an invalid key disables the plugin or reports a warning.
Restart and verifyUse /nclaims status, /nclaims modules and /nclaims hooks before opening the world to players.

First Setup#

A reliable order prevents protection checks from running before the storage and world policy are ready.

Do not enable war overlay actions or paid claim creation until a backup and an economy test have passed.
  1. Choose the storage provider and table prefix.
  2. Set the claim world policy and capacity rules.
  3. Enable chunk claims, selection claims and protection.
  4. Configure roles, member actions and trusted players.
  5. Add economy pricing, upkeep, sale or rent only if needed.
  6. Test with a non-admin account in wilderness and inside a claim.

Minimal policy#

modules:
  territory.chunk-claim: true
  territory.selection: true
  protection: true
  economy: false
  nations: false
  warfare: false

claim:
  default-capacity: 16
  allow-auto-claim: false

Claims & Protection#

Players can claim a current chunk, a radius or a two-point selection. The protection listener evaluates ownership, role, environment policy and war overrides before blocking an action.

Protection covers block break, block place, interact, entity interact, entity damage, item pickup and tamed-pet ownership flows. Deny messages are rate-limited to avoid chat spam.

Claim creation#

  • /claim here for the current chunk.
  • /claim radius <n> for an area around the player.
  • /claim wand and /claim selection claim for cuboid selection.
  • Claim map and preview GUI show capacity, cost and wilderness state before confirmation.

Ownership model#

  • Owner, trusted members and role thresholds are stored independently.
  • Per-claim action overrides live in permissions.yml.
  • Adjacent owned claims can be merged.
  • Unlimited capacity is permission-gated, not silently enabled.

Quality-of-life#

  • Auto-claim can claim wilderness as a player enters it.
  • Border particles and temporary client-side fallback visualize boundaries.
  • Starter chest, trapped rescue, claim chat, favorites and top lists are available.
  • Claim core, public state, warps, fly and vaults are separate controls.

Economy & Lifecycle#

Economy is a soft hook. If no provider is available, paid actions stay disabled instead of charging a player through a fallback that cannot be verified.

Test deposits, withdrawals, sale commission, rent expiry and upkeep with a low-value test claim before production rollout.

Supported flows#

  • Optional creation pricing: base, per-chunk and progressive existing-chunk cost.
  • Claim bank deposits, withdrawals and upkeep processing.
  • Sale marketplace with commission, listing, purchase and cancellation.
  • Rent offers with accept, leave, expiration and owner/tenant notifications.
  • Private/public warps with optional teleport fees.
  • Vault inventory persistence and trusted access.

Lifecycle controls#

  • Renewal windows and one/seven/thirty-day actions.
  • Temporary camps with expiration events.
  • Audit entries for economy, warp, rent and lifecycle actions.
  • Migration commands create timestamped YAML backups before import.
/claim renew 30
/claim rent offer 250 7
/claim bank
/claim audit 25

Nations & War#

Nations group lands and add diplomacy/bank state. Wars create explicit records with capture scores and a separate overlay policy.

War records can be enabled while destructive block and entity overlay actions remain disabled. Treat overlay flags as a deliberate server-rule decision.

Nation operations#

  • Create, list and inspect nations.
  • Add land to a nation and manage capital land.
  • Store diplomacy state in diplomacy.yml.
  • Use nation bank operations through the active economy provider.
/nation create Ember
/nation addland Ember
/nation diplomacy list
/nation deposit 500 Ember

War safety baseline#

war:
  enabled: true
  overlay:
    allow-block-break: false
    allow-block-place: false
    allow-entity-damage: false

Declare land-vs-land, land-vs-nation or nation-vs-nation conflicts, then inspect score, capture, surrender and end operations from the admin workflow.

Commands#

The command surface is split into player claims, economy, nations, war and operations.

Aliases include /claims, /nclaim, /land, /nexaclaims, /nclaimnation and /claimwar.
/claimPlayer surface
Actions

here, chunk, preview, radius, wand, selection, map, list, manage, info, trust, untrust, unclaim, merge, auto.

Examples

/claim preview
/claim trust Alex officer

Purpose

Create, inspect and manage player territory.

/claim bank · rent · warp · vaultEconomy
Actions

deposit, withdraw, upkeep, sell, buy, cancel-sale, rent, warp, fly, vault, renew, camp.

Examples

/claim sell 2500
/claim warp list

Purpose

Run optional claim services.

/nation · /warPolitical layer
Actions

create, info, list, addland, diplomacy, bank, declare, history, top, capture, score, surrender, end.

Examples

/war declare land 12
/war score abc123

Purpose

Manage grouped lands and conflicts.

/nclaimsAdmin
Actions

status, modules, storage, hooks, debug, migration, web, menu-editor, reload, version.

Examples

/nclaims hooks
/nclaims web status

Purpose

Diagnose and operate the plugin.

Permissions#

Normal player actions default to true where the server can safely expose them; admin, bypass, audit, migration and web operations default to op.

/lp group admin permission set nexaclaims.admin true
/lp group default permission set nexaclaims.claim.create true

Player access#

nexaclaims.use, nexaclaims.claim.create, nexaclaims.claim.selection, nexaclaims.chat, nexaclaims.favorite, nexaclaims.vault, nexaclaims.warp, nexaclaims.marketplace, nexaclaims.rent, nexaclaims.template, nexaclaims.lifecycle, nexaclaims.camp and nexaclaims.nation.

Admin access#

nexaclaims.admin, nexaclaims.reload, nexaclaims.admin.menu-editor, nexaclaims.region, nexaclaims.audit, nexaclaims.migration, nexaclaims.web and nexaclaims.capacity.*.

Risk controls#

nexaclaims.bypass.protection, nexaclaims.fly, nexaclaims.war, nexaclaims.flags, nexaclaims.signs, nexaclaims.ban and nexaclaims.unlockdrops should be assigned deliberately.

Configuration#

Keep player-facing text, menu behavior, modules and integration policy separate so reloads remain predictable.

config.yml

License, storage, economy, claim cost, capacity, borders, upkeep, marketplace, lifecycle, rent, camps, war, web panel and world policy.

modules.yml

Toggle territory, protection, GUI, economy, nations, warfare, storage and audit modules.

integrations.yml

Optional hooks, command templates and bridge behavior for maps, shops, holograms, Discord and proxy sync.

permissions.yml

Per-claim action-role overrides. Keep this file with backups when changing role behavior.

Storage & Migration#

YAML persistence is convenient for small servers; normalized JDBC adapters are available when claim, audit and war datasets grow.

Back up all YAML and the database before switching providers, running migrations or changing table prefixes.

Data surfaces#

  • Lands and chunks
  • Members, roles and permission overrides
  • Vaults, warps, lifecycle, rent and camps
  • Nations, diplomacy and wars
  • Economy ledger and audit entries
  • Favorites and migration state

Safe migration#

  1. Run /nclaims storage and /nclaims migration adapters.
  2. Review /nclaims migration preview.
  3. Create an external backup.
  4. Run the import during a maintenance window.
  5. Verify counts, ownership and protection before enabling players.

Integrations#

Hooks are detected safely and unavailable providers do not prevent startup.

Economy & permissions#

Vault/VaultUnlocked, LuckPerms and PlaceholderAPI can provide currency, context, metadata, claim capacity and scoreboard values.

Maps & presentation#

dynmap, BlueMap, Pl3xMap and squaremap marker adapters; DecentHolograms, HolographicDisplays, CMI and ArmorStand fallback for marketplace displays.

Network & gameplay#

Redis publish/locks, Discord webhooks, Geyser/Floodgate forms, ItemsAdder/Oraxen/Nexo materials and QuickShop-Hikari protection bridges.

Developer API & Events#

The public API is registered through Bukkit ServicesManager and exposes focused services instead of forcing consumers to access managers directly.

Service access#

NexaClaimsApi api = Bukkit.getServicesManager()
    .load(NexaClaimsApi.class);

if (api != null && api.claims().isClaimed(location)) {
    // Read the public territory state.
}

Services cover claims, territory, memberships, permissions, environment rules, economy, vaults, lifecycle, rent, nations, wars and audit queries. Always handle a missing service during reload or disabled-module states.

Events#

Listen for land create/delete, chunk claim/unclaim, member add/remove, permission changes, sub-area creation, vault transactions, rent lease create/expire, camp expire, nation create, war declare/start/end and admin actions.

Cancel or validate before mutating external state, and never assume an optional integration is present.

Quick Start#

Create a protected claim and prove owner, member and outsider behavior.

Admin bypass can hide protection mistakes.
Check hooksConfirm enabled worlds, economy, limits and costs.
Preview/createUse /claim preview, then /claim here; selections use /claim wand and /claim selection claim.
Test trustOpen /claim manage, run /claim trust <player> [role] and test blocks/containers as outsider.

Player Claim Setup#

Separate private claims from shared access, economy and travel.

Use the smallest trust role that works.

Owner flow#

  1. Preview capacity, price and boundary.
  2. Create and inspect before setting a home.
  3. Add members with the smallest role.
  4. Test containers, doors, redstone and animals.
  5. Confirm /claim info and manage menu.

Economy lifecycle#

  1. Test /claim deposit/withdraw on disposable claim.
  2. Enable renewal notices.
  3. Test sale/rent with two accounts.
  4. Back up before storage changes.

Nation & War Setup#

Roll out nation, diplomacy and war without destructive actions too early.

Start scoring/capture in a test world; add overlays after rollback is proven.
Nation preparation social layer
  1. Create a test nation with /nation create Ember.
  2. Add members and verify treasury/diplomacy permissions.
  3. Test alliance/enemy changes and protection.
War rehearsal safe rollout
  1. Declare war with destructive overlays disabled.
  2. Verify score, capture, surrender and end.
  3. Inspect audit/history before enabling world actions.

Production Rollout#

Make claims predictable under load, migration and staff intervention.

Back up configuration and persistent data before economy or lifecycle changes.

Go-live#

  • Use explicit world/region rules.
  • Keep economy errors visible.
  • Test expiration, unclaim, transfer and restart.
  • Document trust and war policies.

Baseline#

storage: type: sqlite claims: prevent-overlap: true notify-before-expire: true economy: require-vault: true

Operational Reference#

A practical claim-owner flow for wilderness, members, economy services and war-safe operation.

Test every flow once with a normal player account and once with an admin/bypass account; bypass permissions can hide protection mistakes.

Player claim workflow#

  1. Use /claim preview in wilderness to inspect capacity and price.
  2. Confirm with /claim here, or use /claim wand followed by /claim selection claim for a selected area.
  3. Open /claim manage, add members with /claim trust <player> [role] and verify role actions.
  4. Test a protected block, container and pet with a non-member account.
  5. Set a home/warp only after ownership and permission checks pass.

Economy and lifecycle workflow#

  1. Confirm Vault/economy status with /nclaims hooks.
  2. Test /claim deposit, /claim withdraw and upkeep on a disposable claim.
  3. Create a low-value sale or rent listing, accept it from another player and verify audit entries.
  4. Renew lifecycle-managed claims before enabling expiration notifications.
  5. Back up YAML/database data before migration or table-prefix changes.

Nation and war rollout#

Create nations and diplomacy records first. Declare a test war while all destructive overlay flags are disabled, verify score/capture/surrender/end, then enable only the world actions your rules and rollback process support.

/nation create Ember
/nation addland Ember
/war declare land 12
/war info <id>
/war surrender <id>

Open /nclaims menu-editor, move one item, save, reload and reopen the same menu. If an item disappears, validate its material, action, module visibility and permission before changing slots again.

Troubleshooting#

Start with the plugin status, hook diagnostics and the complete console stack trace.

When reporting an issue include plugin version, Paper build, Java version, storage type, enabled modules, integration list and reproduction steps.

Claims are not protected#

Check protection: true, the world policy, module state and /nclaims hooks. Test with a non-admin account because bypass permissions override denies.

Confirm Vault and an economy provider are loaded, the economy module is enabled and the player has enough balance. A missing provider intentionally disables charging.

GUI item is missing#

Validate material, slot, action and module visibility in menu.yml. Disabled modules and missing permissions hide items by design.

War changes the world unexpectedly#

Review the war.overlay flags. Keep block and entity overlay actions false until the server rules and rollback procedure are ready.

Migration cannot be trusted#

Run preview first, compare counts with the source, keep the generated backup and test ownership/protection before importing a second time.

Reload did not apply a change#

Use /nclaims reload for supported YAML changes. Storage provider, table prefix and some world policy changes should be applied with a full restart.

Support#

Give support enough context to reproduce the issue without exposing license keys or database passwords.

Documentation URL: www.ritomasss.com/docs/nexaclaims

Include#

  • Plugin, Paper and Java versions
  • Storage type and enabled modules
  • /nclaims status, modules and hooks output
  • Relevant YAML section with secrets removed
  • Full error and exact reproduction steps

Never include#

License keys, database passwords, webhook tokens, Redis credentials or private player data. Replace them with REDACTED before sharing logs.