# 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.0.3** adds a separate Folia build, joined claim outlines, filtered claim lists, a personal access summary and a short administrator diagnostic command while preserving existing aliases and claim data. --- ## New in 1.0.3 **See your land as one area.** `/claim see` hides internal edges between nearby side-connected claims with the same owner. Particle and temporary-block displays remain bounded by time, distance and workload limits. **Find the right claim.** Filter your own list by name, world or sale status: `/claim list name home`, `/claim list world world_nether`, `/claim list sale listed`. Numbers continue to match `/claim tp`; filtering never renumbers destinations. English/Turkish filter words and TAB suggestions are supported. **Understand your access.** `/claim info` shows your effective rights and remaining temporary trust duration, without revealing other players' trust records to visitors. **Get a concise support summary.** `/claim admin diagnose` (Turkish: `tanı` / `tani`) works for permitted administrators and the console. It shows storage, economy and installed integrations, without secrets or filesystem paths. Installed does not mean verified compatible. ## Choose your server build | Server | JAR | |---|---| | Bukkit, Spigot, Paper, Purpur | `DyClaim-1.0.3.jar` | | Folia | `DyClaim-1.0.3-Folia.jar` | 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 EN/TR 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](https://github.com/DyPlugin/DyClaim/blob/1.0.3/docs/platforms.md) · [Command guide](https://github.com/DyPlugin/DyClaim/blob/1.0.3/docs/claim-management.md) · [Downloads and checksums](https://github.com/DyPlugin/DyClaim/releases/tag/1.0.3) ## 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** and **Turkish** are supported out of the box, including translated operation words and trust rights. TAB shows the active language while both languages 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, and Floodgate enables Bedrock detection and block borders. Installed integrations are detected automatically; core claiming works without them. --- ## A measured look at protection ![Processing time for 1,000 block-break checks across four plugins](https://github.com/DyPlugin/DyClaim/blob/main/docs/images/DyClaim-4-plugins-en.png?raw=true) 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](https://github.com/DyPlugin/DyClaim/blob/v1.0.2/docs/benchmark-50-claims.md) ## Claim your land, your way Claim your current chunk with `/claim`. Server owners can configure prices, cooldowns, total/world limits 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. 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. 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. 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. ## English and Turkish, automatically With `lang: auto`, players receive messages and TAB suggestions based on their saved preference or Minecraft language. Turkish clients receive Turkish; other languages fall back to English. **TAB shows only the effective language. Both languages still work when typed.** This includes operation words and trust permission names. Players can choose `/claim lang auto|en|tr`. Administrators can force a language for everyone with `/claim admin lang en|tr`, taking priority over personal preferences. Choosing `auto` restores automatic selection. Turkish equivalents and ASCII spellings are accepted. ## Commands | Command | Purpose | |---|---| | `/claim` | Claim your current chunk | | `/claim sell`, `/unclaim` | Sell back or remove your claim | | `/claim trust [duration]` | Grant permanent or temporary access | | `/claim trust ` | Change individual trust rights | | `/claim untrust `, `/claim trustlist` | Manage trust | | `/claim coowner add `, `/claim coowner remove` | Manage one coowner | | `/claim transfer ` | Offer an ownership transfer | | `/claim market list `, `/claim market cancel`, `/claim market buy` | Trade claims | | `/claim auto [on\|off]` | Toggle automatic claiming | | `/claim name `, `/claim setspawn` | Set a name or safe spawn | | `/claim tp `, `/claim list [page]` | Navigate your claims | | `/claim info`, `/claim see` | Inspect a claim or display borders | | `/claim pvp`, `/claim explosion [mob]`, `/claim mob` | Change unlocked protection settings | | `/claim villager`, `/claim doors`, `/claim trapdoors` | Change villager/visitor settings | | `/claim warn ` | Warn an unauthorized visitor | | `/claim lang ` | Choose your language | | `/confirm`, `/cancel` | Accept or reject a pending action | 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 | Permission | Default | Purpose | |---|---|---| | `dyclaim.player` | Everyone | Player command group | | `dyclaim.claim` | Everyone | Claim chunks | | `dyclaim.sell` | Everyone | Sell or remove claims | | `dyclaim.see` | Everyone | Display claim borders | | `dyclaim.info` | Everyone | View claim information | | `dyclaim.list` | Everyone | List claims | | `dyclaim.trust` | Everyone | Manage trust and access rights | | `dyclaim.teleport` | Everyone | Teleport to claims | | `dyclaim.settings` | Everyone | Change unlocked claim settings | | `dyclaim.coowner` | Everyone | Manage coownership | | `dyclaim.transfer` | Everyone | Transfer ownership | | `dyclaim.market` | Everyone | Use the player marketplace | | `dyclaim.auto` | Everyone | Use automatic claiming | | `dyclaim.name` | Everyone | Name claims | | `dyclaim.setspawn` | Everyone | Set claim teleport destinations | | `dyclaim.warn` | Everyone | Warn unauthorized visitors | | `dyclaim.admin` | OP | Core administration, player commands and bypass permission | | `dyclaim.admin.bypass` | OP | Protection bypass permission | | `dyclaim.admin.purge` | OP | Additional permission for inactive cleanup | | `dyclaim.admin.purge.exempt` | OP | Inactive cleanup exemption | | `dyclaim.warn.exempt` | OP | Warning-sanction exemption | 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.0.3 verification:** 284 automated tests and artifact checks. Selected Purpur/Folia 1.20.4 scenarios covered claim acquisition, named/sale-filtered lists with stable indices, personal access, denied diagnostics, EN/TR TAB, joined Java particle packets, reload and normal restart persistence. Native modern-server and integration limits are recorded in the [verification notes](https://github.com/DyPlugin/DyClaim/blob/1.0.3/docs/verification-1.0.3.md). **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](https://github.com/DyPlugin/DyClaim/blob/v1.0.2/docs/compatibility-test.md). Optional integrations: | Plugin | Purpose | |---|---| | Vault + economy provider | Payments, refunds and marketplace | | WorldGuard, GriefPrevention, Towny, Lands, Residence, GriefDefender | Overlap prevention hooks | | Floodgate | Bedrock detection and block-border visualization path | | SimpleClans | Experimental clan trust | 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 EN/TR 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. **Upgrading from v1.0.0 or v1.0.1:** 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](https://github.com/DyPlugin/DyClaim/blob/main/LICENSE). 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](https://github.com/DyPlugin/DyClaim)

DyClaim

1.0.3

1.0.3-Folia

v1.0.2

v1.0.1

v1.0.0

v1.0.0-Beta