Tags
Creators
Details
1.0-SNAPSHOT
Compatibility
Required content
Changes
🛡️ Ultimate Protection: Professional Claims System Ultimate Protection is an advanced, lightweight solution for players to protect their builds and belongings. Unlike other protection plugins, it uses a system of informative holograms and interactive visual borders to provide the best user experience.
✨ Key Features Total Terrain Protection: Prevents other players from breaking blocks, placing objects, or interacting with chests and entities within your protected area.
Dynamic Holograms: Each protected terrain displays a floating hologram indicating the owner and protection status, making it easy to identify areas.
Edge Visualization: Using particles, players can see exactly where their boundaries end in real time without the need for external tools.
Flexible Time System: Manage temporary or permanent protections thanks to an advanced time processor (supports formats such as 5m, 1d, 12h, etc.).
Robust Database: Uses SQLite storage to ensure that no protections are lost after a server restart.
Intuitive Administration: Simple commands to create, delete, and manage members on the grounds.
🛠️ Technical Details Compatible Versions: Designed for Paper/Spigot.
Dependencies: The dependencies required to use the plugin would be (Vault,ProtocolLib,PlaceholderAPI)!
[💠 The Energy Core (Hologram System) The Energy Core is a dynamic visual entity that automatically appears in the center of each claimed area. It is not just a decoration; it is the main information panel for players and visitors.]
[🛡️ The Protection System Hologram This system acts as the physical interface for your protected land. Instead of relying solely on chat messages, the plugin displays informative holograms that float directly in the game world.]
Performance: Optimized to prevent lag thanks to efficient event management.
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:aA6lmTVz:h0UNa0LR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aA6lmTVz:h0UNa0LR"
}

