Tags
Creators
Details
1.0.0-beta.3
Compatibility
Required content
Changes
LederProtections v1.0.0-beta.3
Production-hardening beta for Minecraft 1.21.x servers.
Compatibility
- Spigot 1.21.x
- Paper 1.21.x
- Purpur 1.21.x
- Pufferfish 1.21.x
Paper remains recommended for production servers.
Added
- Added
/lep admin, a dedicated administrative protection browser. - Added
lederprotections.admin.protectionspermission for viewing all server protections through the admin GUI. - Added clearer Folia diagnostics while keeping Folia marked as unsupported.
- Added
.gitattributesline-ending normalization for cleaner Git diffs.
Changed
/pis now a personal player protection menu, even for administrators.- Administrators no longer automatically see every server protection in
/p. - Global protection browsing is now separated into
/lep admin. - Improved command permission routing so
/lep info,/lep status, and/lep versioncan uselederprotections.infowithout granting normal player management access. - Improved optional protection ID handling for commands such as rename, transfer, member, co-owner, block, and debug helpers.
- Improved persistence handling so commands and GUIs do not report success if protection saving fails.
Fixed
- Fixed PvP-denied interactions applying knockback in protected areas.
- Reduced spam from repeated PvP-denied messages.
- Prevented shop purchases when the player inventory is full.
- Prevented purchased protection stones from being dropped on the ground when inventory space is unavailable.
- Hardened economy transactions for shop purchases, upgrades, and teleport costs.
- Hardened protection update persistence after rename, transfer, member changes, blocked-player changes, rule changes, debug changes, and GUI changes.
- Improved safe handling of invalid explicit protection IDs to avoid accidentally falling back to the current protection.
Notes
This is still a beta release. Testing on a staging server is recommended before production usage.
Optional dependencies
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:UFhFsET6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7lamm91:UFhFsET6"
}

