DyClaim v1.0.0

Changes from v1.0.0-Beta to the stable release

DyClaim 1.0.0 expands the Beta's chunk claiming system with shared ownership, finer access controls, player trading and additional protection. The familiar command-based workflow, automatic English/Turkish language selection and optional integrations remain available.

Added

Ownership and access

• Temporary trust with durations such as 30m, 2h and 7d, alongside permanent trust.
• Individual trust rights for building, containers, doors, trapdoors, redstone, entities and teleportation.
• One coowner per claim, with recipient acceptance and ownership-limit checks. Coowners can manage trust and settings but cannot sell, delete or transfer the claim.
• Ownership transfers requiring recipient acceptance. Transfers clear previous trust, coownership, clan access and marketplace listings.
• Optional experimental SimpleClans trust.

Claim management and economy

• Player marketplace for listing, cancelling and buying claims, with configurable price limits and tax. /claim sell continues to sell claims back to the server.
• World-specific claim prices and limits, plus optional spacing between different owners.
• Automatic claiming while walking, respecting prices, balance, cooldowns and ownership limits. Free automatic claiming requires explicit configuration.
• Claim names and teleportation by name, in addition to the existing claim-number teleportation.
• Custom safe teleport destinations with /claim setspawn.
• Paginated claim lists.

Protection and administration

• Player damage to villagers blocked by default while trading remains available.
• Separate visitor access settings for doors and trapdoors.
• Separate mob-explosion and visitor/mob farmland-trampling policies.
• Global and world protection defaults, forced rules and locked claim settings.
• Optional mob cleanup in loaded claim chunks, with configurable scope and named/tamed exceptions.
• Session-based protection bypass.
• Temporary and permanent bans on acquiring claims.
• Inactive claim cleanup with preview, confirmation, backups and batch processing; optional scheduled cleanup.
• Visitor warnings with shared cooldowns and configurable sanctions.

Language preferences

• Saved player language preferences through /claim lang auto|en|tr.
• Localized operation words and trust-right names, including ASCII alternatives for Turkish commands.

Improved

• Sensitive actions recheck ownership, permissions, prices, bans and limits when confirmed.
• Confirmations use single-use tokens and notify players when a pending action is replaced.
• Claim storage uses a versioned format, stable claim IDs and atomic file replacement.
• A transaction journal records economy operations and locks claims with uncertain payment outcomes to prevent automatic retries.
• Invalid configuration reloads retain the last valid settings.
• Existing protection hooks block claiming when their overlap checks fail.
• Spigot compatibility uses common server APIs for action bars and version detection.

Fixed

• Selling after moving to another chunk no longer acts on the player's new location.
• Repeated price-difference refunds and failed economy responses being treated as successful payments.
• Protection gaps around cross-owner pistons, fluid flow, hopper transfers and double chests.
• Residence overlap checks missing protected areas outside the chunk center.
• Update checks treating older Beta or release-candidate versions as newer than the stable release.

Upgrading from Beta

Stop the server, back up the old JAR and the entire plugins/DyClaim/ folder, then replace the JAR with DyClaim-v1.0.0.jar. Keep the existing data folder.

Existing claims, owners and trust migrate automatically. The original claim file is preserved as claims.beta-backup.json. Existing configuration values and custom messages are retained; missing settings and messages receive defaults.

Marketplace, automatic claiming, warnings, mob cleanup, scheduled cleanup and clan integration are disabled by default. Enable the features you want in config.yml.

Rolling back to Beta requires the old JAR and matching old-format data. See the upgrade and recovery guide.

Compatibility

The plugin remains compiled for Java 17; use the Java runtime required by your server. Tested environments and integration limitations are documented in the compatibility matrix.

Project · Source and issues