Tags
Creators
Details
1.0
Compatibility
Changes
๐ PrivateChest - Secure Your Chests Like Never Before! ๐ PrivateChest is a lightweight and efficient plugin that allows players to protect their chests (single or double) from unwanted access or destruction โ even from explosions! Compatible with Spigot and popular forks like Paper, Pufferfish, and Purpur, from version 1.16.x up to 1.21.5.
โ Features ๐ก๏ธ Complete Chest Protection โ Prevents other players from opening or breaking protected chests.
๐ฅ Explosion-Proof โ TNT and creeper explosions won't destroy protected chests.
๐ Simple Command-Based System โ Protect and unprotect your chests with easy-to-use commands.
๐งพ Permission Support โ Full compatibility with permission plugins like LuckPerms.
โ๏ธ Customizable Configuration โ Adjust messages and behavior to your liking.
๐ฆ Lightweight and Fast โ Optimized to have minimal impact on server performance.
๐ Multi-Version Support โ Works on servers from 1.16.x to 1.21.5.
๐ ๏ธ How to Use Protect a chest:
bash
Copiar
Editar
/privatechest protect
Unprotect a chest:
bash
Copiar
Editar
/privatechest unprotect
๐ Just look at the chest and run the command!
๐ Permissions
Permission Description Default privatechest.use Allows using the /privatechest commands true privatechest.admin Allows managing other players' protections op ๐งฉ Compatibility โ Tested with:
Spigot
Paper
Purpur
Pufferfish
๐ Supports Minecraft 1.16.x - 1.21.5
๐ฌ Support & Suggestions If you have suggestions or find a bug, feel free to post in the discussion section or contact me directly via DM. Iโll do my best to help!
๐ฅ Download & Installation Download the .jar file.
Drop it into your /plugins folder.
Restart or reload your server.
Enjoy secure storage!
โค๏ธ Like the Plugin? Leave a โญ๏ธ review to support the project and help others discover it!
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:TfUGyoNj:GH79NwB9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TfUGyoNj:GH79NwB9"
}

