Tags
Creators
Details
v1.0.1
Compatibility
Changes
Maintenance update for v1.0.0, focused on claim protection and reliable update notifications.
Fixed — Update notifications
- Fixed malformed Modrinth API requests that prevented update detection.
- Corrected Minecraft version detection for modern server version strings.
- Update checks now select the newest compatible public stable release, regardless of API response order.
- Notifications link directly to the matching Modrinth version.
- Fixed duplicate
vprefixes in displayed version numbers. - Administrators already online receive notifications when an update check completes. Administrators joining later are also notified.
- Added periodic checks and retries for failed requests, with failures reported in the console.
- Prevented repeated notifications for the same update within a login session.
- Update-checker settings now apply correctly on reload.
Fixed — Claim protection
- Closed protection gaps when placing beds and other structures spanning multiple blocks across claim boundaries.
- Protected against unauthorized block changes using axes, hoes, shovels, bone meal, shears, honeycomb and sign-coloring items.
- Required build access when editing existing signs.
- Extended PvP protection to player-owned wolves and harmful splash and lingering potions, while allowing beneficial potions.
- Protected vehicles against player-fired projectiles and unauthorized entry.
- Applied entity access permissions to farm-animal damage, protected entity interactions and leash operations.
- Applied explosion settings to protected animals, vehicles and decorative entities.
- Added configurable protection against dispenser output and tree or fertilization growth crossing ownership boundaries.
- Protected claim animals against distant dispenser projectiles and applied PvP restrictions to dispenser-fired attacks.
Compatibility
- Existing v1.0.0 claims and player data remain compatible.
- Missing configuration options are added without overwriting existing settings.
- Existing commands, permissions and automatic English/Turkish language support are preserved.
- The plugin continues to target Java 17 bytecode.
Upgrading
Replace the existing DyClaim JAR while the server is stopped, then restart the server. Back up your plugins/DyClaim folder before upgrading.
Users running v1.0.0-Beta or the original v1.0.0 must update manually once. The update-checker defect exists inside those older JARs, so they may not announce this release. After installing v1.0.1, the corrected checker can notify administrators about future compatible stable releases.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:qSfyGIad:K6WNhrKh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qSfyGIad:K6WNhrKh"
}

