Tags
Creators
Details
1.3.0
Compatibility
Required content
Changes
LederProtections v1.3.0
This update introduces per-protection environment settings for hostile mobs, explosions, and fire.
New Environment Settings
A new Environment menu is available from the protection management GUI.
Each setting has three states:
- Enabled
- Disabled
- Default
The Default state inherits the server-wide configuration.
Available Settings
- Hostile Spawning
- TNT Explosions
- Creeper Explosions
- Other Explosions
- Fire Spread
Hostile Spawning
- Control hostile mob spawning separately for each protection.
- Supports natural spawning, spawners, spawn eggs, dispensers, raids, patrols, and reinforcements.
- Passive animals, villagers, golems, bees, and wolves are unaffected.
- Mobs created through commands or compatible custom-mob plugins are not blocked.
- Visitors still need the appropriate permission to use spawn eggs.
Explosion Settings
- Separate controls for TNT, creepers, and other explosion types.
- Supports regular TNT, TNT minecarts, redstone activation, dispensers, beds, respawn anchors, End Crystals, fireballs, wither skulls, and withers.
- Disabled explosions cannot destroy protected blocks, decorations, armor stands, or vehicles.
- End Crystals cannot be activated or destroyed while Other Explosions is disabled, preventing their explosion damage.
- Player and creature damage remains controlled by the existing combat rules when an explosion is allowed.
Fire Spread
- Control fire spreading, environmental ignition, and block burning.
- Includes fire caused by adjacent flames and lava.
- Manually lighting fire still requires the normal player permissions.
- Grass, mycelium, sculk, mushrooms, and natural growth are unaffected.
Boundary Protection
Environmental effects cannot cross protection boundaries:
- Outside effects cannot enter a protection.
- Effects from inside a protection cannot damage the outside.
- Effects cannot travel from one protection into another.
- Effects within the same protection follow its configured setting.
- Events occurring completely outside protections are unaffected.
Moving explosives and projectiles retain their original source, preventing TNT cannons and similar mechanisms from bypassing protection boundaries.
GUI Improvements
-
Added an Environment button to the protection management menu.
-
Added clear icons and descriptions for every environment setting.
-
The menu displays only the current state and server default.
-
Settings cycle through:
Default → Enabled → Disabled -
Owners, administrators, and authorized co-owners can manage these settings.
-
Members and visitors cannot modify them.
Configuration and Data
- Existing protections automatically use the new server defaults.
- Per-protection settings persist after server restarts.
- Changing a server default and running
/lep reloadupdates every protection using Default. - Existing configuration files are updated without overwriting customized values.
- Invalid setting names or values are ignored safely and reported in the console.
- Native protection exports and imports preserve environment settings.
- No destructive protection-data migration is required.
Back up your server files before updating.
Gracias a xywm112
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:2cRH9cA3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7lamm91:2cRH9cA3"
}

