Tags
Creators
Details
1.0.0-beta.4
Compatibility
Changes
LederProtections v1.0.0-beta.4
This update focuses on admin usability, player experience, permission-based limits, notifications and general beta polish.
Added
- Added
/lep admin, a dedicated admin protection browser. - Added filters and sorting to the admin protection browser.
- Added creation date display in the admin protection browser.
- Added permission-based protection limits.
- Added action bar messages when entering or leaving protections.
- Added player notification preferences in
/p. - Added public support files, issue templates and contribution documentation.
Changed
/pnow only shows protections where the player has a normal relationship, such as owner, co-owner or member.- Admins now use
/lep adminto view all server protections. - Improved chat messages to be shorter, cleaner and more contextual.
- Improved Spanish and English translations.
- Improved
/lep adminlocalization for filters, sorting and protection information. - Improved documentation and compatibility notes.
Fixed
- Fixed missing Spanish notification preference messages.
- Fixed admin protection browser filter labels showing technical names.
- Fixed the admin browser viewer head showing as a default Steve head.
- Fixed
.gitignoreformatting and repository cleanup issues. - Removed duplicated issue template files.
Security and Stability
- Improved command permission handling.
- Improved optional protection ID handling.
- Improved persistence handling for protection updates.
- Improved economy transaction safety.
- Improved GUI safety and player preference persistence.
Compatibility
- Spigot 1.21.x
- Paper 1.21.x
- Purpur 1.21.x
- Pufferfish 1.21.x
Paper is recommended for production servers.
Folia is not supported yet.
Notes
This is still a beta release. Testing on a staging server is recommended before production usage.
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:n73JqfZ5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7lamm91:n73JqfZ5"
}

