Description
Current Task: Better page handler
Private Chest provides a secure, personal storage solution for your server.
Using the /chest command, players can access their own multi-page private chest from anywhere and safely store valuable items.
Chest data can be stored using either Sqlite or a MySQL database, allowing server owners to choose the storage method that best fits their setup.
Overview
| ✨ Features |
|---|
| Personal private chest for every player |
| Multiple chest pages (permission-based access) |
| Admin access to player chests |
| SQLite (default) or MySQL database support |
| Persistent data across restarts and crashes |
| Page-based permission system |
📦 Storage Options
| Sqlite (Default) | Mysql |
|---|---|
| Simple file-based local storage | Centralized database storage |
| Zero configuration required | Suitable for larger or multi-server setups |
| Lightweight | Requires MySQL configuration |
Storage type can be selected in databaseConfig.json
For Sqlite "Database Type": "Sqlite"
For Mysql "Database Type": "Mysql"
>_ Commands
| Commands | Permission | Description |
|---|---|---|
/chest |
privatechest.use | Open your private chest |
/chest pageNumber |
privatechest.use.page |
Open a specific chest page |
/chest pageNumber playerName |
privatechest.use.admin | Open another player’s chest (Admin) |
/chest pageNumber viewerName ownerName |
privatechest.use.admin | Show player's chest to another player (Admin) |
🔒Permission Structure
Page access is permission-based:
privatechest.use.1
privatechest.use.2
privatechest.use.3
...
🚧 Planned Improvements
- Plugin API for developers
- Performance optimizations
- Improved page handler system
- Extended database validation & safety checks
⚠️ Disclaimer
- Sqlite and MySQL support may contain bugs
- Always keep backups before switching database types.
Please report issues via the GitHub Issues page: 👉https://github.com/genkuqq/Private-Chest/issues


