DyClaim — Chunk Claiming Made Simple

Protect your builds. Share your land. Manage your claims.

DyClaim is a command-based chunk claiming plugin for survival, SMP and economy servers. Protect land, choose who can use it, and manage claim settings without a GUI.

DyClaim combines temporary trust, shared ownership, player trading, automatic claiming and configurable protection with the familiar command-based workflow. Version 1.1.0 adds claim limits by permission, claim messages, visitor bans, PlaceholderAPI, BlueMap/Dynmap/squaremap layers, import from GriefPrevention and ClaimChunk, a developer API and German, Spanish and Russian messages. Every new system has its own switch, and existing commands, settings and claim data are preserved.

https://dynastyplugins.com/dyclaim

New in 1.1.0

Limits by rank. Give a group dyclaim.limit.<number> or dyclaim.limit.unlimited to change its claim limit. The highest permission wins, and players without one keep the default limit.

Claim messages. /claim message <text> shows a short line to visitors when they walk into your claim.

Visitor bans. /claim ban <player> [duration] keeps a player out of your claim, permanently or for a time. A banned player who is inside is moved to a safe spot outside. /claim unban and /claim banlist manage the list.

PlaceholderAPI and web maps. Built-in %dyclaim_...% placeholders show claims, limit, owner, role and more, with no eCloud download. Claims appear as coloured areas on BlueMap, Dynmap and squaremap.

Switch from another plugin. /dyclaim admin import griefprevention or claimchunk previews and then copies existing claims and trust, after a backup. The old plugin's data is not changed.

For developers. A read-only API and four claim events (create, remove, transfer, trust change). API guide

More languages. German, Spanish and Russian join English and Turkish and are picked automatically from the Minecraft language.

MiniMessage. On Paper, Purpur and Folia, messages can use tags such as <green> or <gradient:#55ff55:#55ffff> next to & codes. On Spigot only & codes apply.

Every new system can be turned off in config.yml. Anonymous bStats statistics can be turned off with metrics.enabled: false.

Version 1.0.4 added paged help, the /dyc, /cltp and /dyca shortcuts and clearer English and Turkish messages.

Choose your server build

Install one backend JAR per gameplay server. Stop the server and back up the full DyClaim data folder before replacement. Both use schema-2 data and the same commands. There are no Velocity/BungeeCord companions in this release.

Java 17 bytecode; use the runtime required by your server. Optional integrations must also support your selected platform. Platform details · Command guide · Integrations and import · Downloads and checksums

Why DyClaim?

Zero bloat. No complex GUIs, no unnecessary features. Just clean, fast chunk protection that works. Optional systems stay disabled until you choose to enable them.

Per-claim settings. Each claim has its own PvP, explosion and mob spawning toggles, plus controls for villager damage and visitor access to doors and trapdoors. Players choose how their land works within the server's rules.

Automatic language. DyClaim detects each player's Minecraft language and shows commands and messages in their language. English, Turkish, German, Spanish and Russian are supported out of the box. Turkish also has translated command words and trust rights; TAB shows the active language while English and Turkish words remain accepted when typed.

Works with your server. Optional hooks for WorldGuard, GriefPrevention, Towny, Lands, Residence and GriefDefender help prevent overlapping claims. Vault connects economy features, Floodgate enables Bedrock detection and block borders, PlaceholderAPI gets DyClaim placeholders, and BlueMap, Dynmap and squaremap show claims on the web map. Installed integrations are detected automatically; core claiming works without them.

A measured look at protection

Measured again with 1.1.0 on Purpur 1.20.4 with 50 claim areas, DyClaim had the lowest observed median in this synthetic workload: 50% owner-allowed and 50% visitor-blocked block-break checks, including default denial feedback. GriefPrevention was faster in the owner-only checks. These are event-processing durations, not CPU or RAM usage, and do not establish superiority across all workloads.

Method, results and limitations

Claim your land, your way

Claim your current chunk with /claim. Server owners can configure prices, cooldowns, total/world limits, limits per rank through dyclaim.limit.<number> permissions and spacing between different owners. Add Vault and an economy provider for paid claims and refunds, or use core claiming without economy dependencies.

Name your claims, choose safe spawn points and teleport by number or name. Paginated lists show locations, while claim information displays ownership, effective settings and sale status. Entry action bars show the owner and PvP state, and owners can add a short welcome message with /claim message. Java particle borders help players see chunk boundaries; an optional Floodgate path provides block borders for Bedrock players.

Automatic claiming can acquire eligible chunks as you walk. It respects balance, limits, cooldowns and acquisition rules, and requires explicit configuration for free automatic claims.

Share access without giving away ownership

Use permanent trust or grant temporary access for 30m, 2h or 7d. Control building, containers, doors, trapdoors, redstone, entities and teleportation separately. A player trusted to open doors does not automatically gain access to chests.

Invite one coowner with their acceptance, or offer ownership to an online player. Coowned claims count toward limits. Coowners can manage trust and settings but cannot sell, delete or transfer the claim. Transfers clear previous trust, coownership, clan access and sale listings.

To keep someone out completely, /claim ban <player> [duration] stops them from walking or teleporting into the claim. Owners, coowners and administrators cannot be banned.

An optional SimpleClans adapter adds experimental clan trust.

Protection with clear controls

• Block placement, breaking, containers and supported entity interactions.
• Per-claim PvP, explosion, mob explosion and hostile mob spawning settings.
• Player villager damage blocked by default, without blocking trading.
• Separate visitor access for doors and trapdoors.
• Separate visitor and mob farmland trampling policies.
• Cross-owner piston, fluid and hopper checks; both halves of double chests are protected.
• Checks for every affected block when placing beds and other multi-block structures.
• Access checks for supported block transformations and sign editing.
• PvP protection for player-owned wolves and harmful splash or lingering potions.
• Entity access checks for farm animals, vehicles and leash operations.
• Configurable boundary protection for dispenser output and external tree or fertilization growth.
• Global/world defaults, forced protection rules and locked player toggles.

Optional mob cleanup uses bounded checks in loaded claim chunks, with configurable scope and named/tamed exceptions. It can also remove eligible mobs already inside a claim. External redstone checks cover nearby power effects rather than every possible circuit.

Trade claims and manage your server

Enable the player marketplace to list, cancel and buy claims. Configure price limits and tax deducted from seller proceeds; /claim sell keeps its server-refund purpose. Purchase confirmations recheck their context, and a transaction journal records uncertain economy outcomes for reconciliation.

Administrators can manage claims, prices, refunds, world blacklists and configuration. Additional tools include session bypass, acquisition bans and inactive cleanup with previews, confirmation, backups and batches. Scheduled cleanup is available separately. Servers moving from GriefPrevention or ClaimChunk can import existing claims with /dyclaim admin import, with a preview and a backup first.

Optional visitor warnings let owners/coowners warn unauthorized players inside their claim. Shared cooldowns prevent alternating owners from accelerating sanctions. Default rules use three warnings within 180 seconds, a 60-second cooldown and a two-day sanction.

Five languages, automatically

With lang: auto, players receive messages based on their saved preference or Minecraft language. English, Turkish, German, Spanish and Russian clients get their own language; other languages fall back to English. Turkish clients also get Turkish TAB suggestions and command words.

TAB shows only the effective language. English and Turkish command words both work when typed. This includes operation words and trust permission names.

Players can choose /claim lang auto|en|tr|de|es|ru. Administrators can force a language for everyone with /claim admin lang en|tr|de|es|ru, taking priority over personal preferences. Choosing auto restores automatic selection. Turkish equivalents and ASCII spellings are accepted.

Commands

/dyc works as a short form of /claim, for example /dyc list. Administrators can use /dyca as a short form of /claim admin; it is hidden from players without dyclaim.admin. Use /claim help and /claim admin for in-game help. TAB suggestions are filtered by permissions and language. The old trustperm / güvenizin and mobexplosion / mobpatlama aliases still work; help and root TAB use the grouped commands. Trust rights are build, containers, doors, trapdoors, redstone, entities and teleport.

Console senders can use claim admin reload and the supported global configuration commands (enable, disable, price, pricediff, cooldown, prefix, economy, lang, blacklist), subject to the existing admin permission checks. Commands needing a player, location or player confirmation remain player-only.

Permissions

Permissions can be configured through your permission manager. A permission does not enable an optional feature that is disabled in configuration.

Compatibility and integrations

1.1.0 verification: 328 automated tests and artifact checks, plus live tests on Paper 1.20.1-26.3, Purpur 26.2, Spigot 26.2/26.3 and Folia 26.2/26.3. They covered rank limits, claim messages, visitor bans, placeholders, BlueMap/Dynmap/squaremap, Vault economy and the market, SimpleClans, imports with trust from GriefPrevention and ClaimChunk, upgrades from Beta, 1.0.3 and 1.0.4, and servers with up to 50,000 claims. Limits are recorded in the verification notes.

Minecraft version listing: 1.20–26.3. Bukkit, Spigot, Paper and Purpur. Compiled for Java 17 bytecode against Spigot API 1.20.4; use the Java runtime required by your server.

Historical v1.0.2 verification: 148 automated tests, plus targeted Purpur 1.20.4 / Java 21 scenarios for console reload, grouped commands, legacy aliases, localized help/TAB and custom-message preservation. Earlier v1.0.2 checks covered restart persistence, visitor access and ghast projectile block protection.

Earlier releases were checked on Purpur 1.20.4 and Paper/Purpur/Spigot 26.2; the maintainer also reported running an earlier release on 26.3. Those checks were not repeated for every version with v1.0.2. Intermediate patch versions were not individually tested. The 26.2 checks used protocol clients through ViaVersion/ViaBackwards. Detailed test matrix.

Optional integrations:

Core claiming requires none of these plugins. Real-provider version compatibility and Bedrock client visualization are not covered by the completed server test matrix; validate your selected integrations before deployment.

Setup and upgrades

1. Stop your server and place the JAR in plugins/.
2. Start the server to generate plugins/DyClaim/.
3. Edit config.yml and the message files as needed.
4. Run /claim admin reload as a permitted player, or claim admin reload in the server console.

Marketplace, auto claim, warnings, mob cleanup, scheduled purge and clan integration are disabled by default. Enable the features you want in configuration. Claim messages, visitor bans, placeholders and map layers are enabled by default and can each be turned off.

Upgrading from v1.0.0 or later: back up the JAR and complete DyClaim data folder, then replace the JAR while the server is stopped. Existing claim data remains compatible; missing configuration options are added without replacing your settings.

Before upgrading from Beta, back up the old JAR and the complete DyClaim data folder together. Existing claims migrate with an old-format backup. Reverting to Beta requires matching old-format data, not just the old JAR.

Update notifications

DyClaim checks Modrinth for the newest compatible public stable release and notifies administrators with a direct version link. It does not replace your JAR automatically. Beta and original v1.0.0 users must update manually once: their installed checker defect cannot be repaired remotely. The corrected checker in v1.0.1 and later can announce future compatible stable releases. Publishing only on GitHub does not trigger Modrinth notifications.

Source code and license

DyClaim uses the custom DyClaim Source-Available License 1.0. Use and modification are permitted, including on commercial servers. Redistribution must be free, retain attribution and provide the corresponding source under the same terms. Paid distribution requires separate written permission. Third-party licenses and rights granted for earlier distributions remain unaffected. Contributions, bug reports and feature requests are welcome.

Source code and issues