Tags
Creators
Details
2.0
Compatibility
Changes
š PrivateChest 2.0 - Major Update!
š What's New
š Enhanced Security
- Password Encryption: All passwords are now securely hashed using SHA-256 with salt. Your old passwords will work and be automatically upgraded when used.
- Better Data Protection: Significantly improved security against potential data breaches.
š„ Trust System
- Share Access Safely: Give other players access to your locked chests without sharing passwords
- New Commands:
/trust <player>and/untrust <player> - Easy Management: Use
/trust listto see who you trust,/untrust allto remove everyone
š Sign Protection
- Visual Locking: Place a sign with
[Private]on the first line near your chest to lock it - No Commands Needed: Perfect for players who prefer visual interactions over typing commands
- Break to Unlock: Simply break the sign to unlock your chest
š Chest Limits
- Permission-Based Limits: Control how many chests players can lock based on their rank/permissions
- Perfect for Economy Servers: Reward VIP players with more chest locks
- Admin Control: Set custom limits from 1 to unlimited chests per player
ā” Performance Improvements
- SQLite Support: Optional database storage for servers with many locked chests (better performance)
- Optimized Code: Faster chest interactions and reduced memory usage
- Smart Caching: Improved response times for large servers
š§ Developer API
- Public API: Other plugins can now safely interact with PrivateChest
- Better Integration: Perfect for custom plugins and advanced server setups
š„ Migration from v1.x
ā Fully Automatic Migration
- All your existing locked chests will continue working normally
- Passwords are automatically upgraded to secure format when used
- No manual configuration needed - just replace the plugin file
- All new features are disabled by default for compatibility
Migration Steps:
- Backup your
plugins/PrivateChest/folder (recommended) - Stop your server
- Replace the old PrivateChest.jar with v2.0.0
- Start your server
- Enable new features in
config.ymlif desired
āļø Configuration
New options in config.yml:
storage-type: yaml(or "sqlite" for better performance)enable-sign-protection: trueenable-chest-limits: falsedefault-chest-limit: 5
šÆ Permission Examples
# Chest Limits (when enabled)
privatechest.limit.unlimited # No limits
privatechest.limit.100 # Up to 100 chests
privatechest.limit.25 # Up to 25 chests
privatechest.limit.10 # Up to 10 chests
privatechest.limit.5 # Up to 5 chests
š Bug Fixes
- Fixed rare double chest synchronization issues
- Improved hopper protection reliability
- Better error handling for corrupted data
- Enhanced explosion protection
š„ This is our biggest update yet! š„
Perfect for survival servers, economy servers, and any server that wants secure, user-friendly chest protection!
Compatible with Minecraft 1.16.x - 1.21.5 | Tested on Paper, Purpur, Pufferfish
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:H85dLRtM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TfUGyoNj:H85dLRtM"
}

