Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated last month
All versions
1.0.0
Release
LederProtections 1.0.04 months ago 12
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Any compatible version
Changes
LederProtections v1.0.0
First stable release of LederProtections.
Highlights
- Protection stones with configurable sizes and behavior.
- Personal protection GUI with
/p. - Separate admin protection browser with
/lep admin. - Member, co-owner and owner role management.
- Protection transfer support.
- Protection upgrades.
- Optional Vault economy support.
- Optional protection shop.
- Teleport support with cooldown and movement checks.
- PlaceholderAPI expansion.
- WorldGuard and WorldEdit integration.
- Internal rule engine for protection actions.
- Modrinth-based update checker.
Protection Rules
- Blocks unauthorized block breaking and placing.
- Protects containers and interactions.
- Handles doors, trapdoors, buttons and levers.
- Handles pistons, hoppers, dispensers and droppers.
- Handles TNT, explosions, fire, lava and water behavior.
- Blocks dispenser projectile damage across protection borders.
- Handles PvP and knockback protection.
- Includes support for fake-player edge cases.
Commands
/popens the player's protection menu./lep adminopens the administrative protection browser./lep checkruns a protection diagnostic./lep versionshows the plugin version and update checker status.
Notes
- The update checker does not download, install or replace plugin files automatically.
- It only checks Modrinth and notifies server administrators when a newer version is available.
- Paper is recommended for production.
- Tested on Spigot, Paper, Purpur and Pufferfish across Minecraft 1.21.x.
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:PsTft005"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7lamm91:PsTft005"
}

