Tags
Creators
Details
1.6.2
Compatibility
Changes
š¢ PrivateChest 1.6.2 ā Hopper Exploit Patch & Full Container Protection
š”ļø New Protections:
-
š« Hoppers can no longer extract items from any protected container.
-
š Applies not only to chests and barrels, but automatically supports any future container types added to PrivateChest (like furnaces, droppers, shulkers, etc.).
-
š§ Uses smart event handling via InventoryMoveItemEvent to detect and cancel unauthorized item transfers.
š§ Technical Improvements:
Protection now checks container ownership via ChestLocker.isChestLocked(...), ensuring consistent behavior.
No performance impact; event runs only when hoppers are in use.
ā Recommended For:
Any server using hoppers, redstone automation, or container protection systems.
Servers upgrading from 1.6.1 or earlier.
Thank you for using PrivateChest Free!
If you find the plugin helpful, please consider leaving a ā review or joining our support community.
Support available in English and Spanish.
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:8S4fa098"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TfUGyoNj:8S4fa098"
}

