Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated last month
All versions
1.4.0
Release
LederProtections 1.4.0 Warps & Holo2 months ago 77
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
v1.4.0
Public protection directory, holograms, and native environmental policies.
Added
- Added opt-in public protection profiles with configurable titles, descriptions, categories, icons, welcome messages, visit points, and visibility.
- Added the
/warpspublic directory with search, category filtering, sorting, favorites, visit counters, and pagination. - Added configurable public-visit warmups, cooldowns, movement/damage cancellation, cross-world control, and safe destination validation.
- Added administrator controls for featured and hidden directory entries.
- Added Bukkit
TextDisplayholograms with configurable lines, placeholders, range, height, and per-protection state. - Added inheritable per-protection environmental policies for hostile spawning, TNT, creepers, other explosions, and fire spread.
Changed
- Environmental explosion and fire decisions now use LederProtections policies while protection-boundary barriers remain enforced independently.
- Existing bundled configuration and language files receive missing 1.4.0 keys through the safe merge and backup system.
- Existing protections remain private by default until their public profile is explicitly changed.
Fixed
- None (Help on github if you knows)
Notes
- No manual protection-data migration is required.
- Customized
holograms.lineslists are not overwritten.
casqi idea, ty
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:aHi3lHed"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7lamm91:aHi3lHed"
}

