Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated last month
All versions
1.1.0
Release
LederProtections 1.1.0 - ProtectionStones migration tools3 months ago 84
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Any compatible version
Changes
LederProtections v1.1.0
Added
- Added ProtectionStones migration tools.
- Added
/lep migrate protectionstones scan. - Added
/lep migrate protectionstones import --dry-run. - Added
/lep migrate protectionstones import. - Added single-region migration support with
--region. - Added strict exact-radius migration by default.
- Added missing-tier detection and suggested
stones.ymlgeneration. - Added ProtectionStones custom name migration from
ps-name. - Added cleanup of old ProtectionStones greeting/farewell WorldGuard flags.
- Added automatic safe source-stone conversion to LederProtections stone materials.
- Added
--keep-source-stones. - Added native LederProtections export/import commands.
Changed
- ProtectionStones migration now skips unmatched radii by default instead of resizing protections.
--mode nearestremains available for advanced migrations, but may resize protections.- Imported ProtectionStones vertical bounds are normalized to the actual world height.
Notes
- Always back up your server before migration.
- Always run dry-run before real import.
- ProtectionStones regions are not deleted automatically.
- Missing custom radii should be added to
stones.ymlor generated withsuggest-stones.
Optional dependencies
Any compatible version
Any compatible version
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:O7lamm91:USYnTO58"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7lamm91:USYnTO58"
}

