Gives every player on the server a 54-slot ender chest instead of the vanila default 27
Features
Up to 54 slots
Swap the 27-slot vanilla ender chest for a configurable GUI of up to 54 slots: a full double chest, six rows instead of three. Players open it the way they always have (right-click an ender chest block, or /ec) and the real block keeps its lid animation. Size is configurable in multiples of 9, from 9 to 54.
Multiple chests per player
Players are no longer limited to a single ender chest. Each can own several, managed through an in-game menu (/eclist):
- Open, rename, and switch between chests from a clean dialog
- Custom icons: pick any item to represent a chest in the list, with a searchable item picker
- Main chest: choose which chest
/ecand block right-click open directly (a new chest is never made main automatically; the player chooses)
Permission-granted chests
Hand out chests by rank instead of by command. The permission enhancedechest.additional_amount.<count>.slot.<size> grants that many chests at that size, e.g. ...2.slot.54 gives two 54-slot chests. Matching nodes stack, grants sync on open, and removing a node removes those chests (spilling any items to a recoverable temporary chest). The player's base chest is always protected.
Admin tools
Manage any player's chests, online or offline:
/ee add//ee resize//ee delete: create, resize, and remove chests (with item-spill safety so nothing is lost)/ee view <player>: open another player's chest yourself;admin.viewfor read-only,admin.editto take and add items- Temporary chests that auto-expire after a duration (e.g.
7d,1h,1d_12h)
Database-backed storage
Every chest's contents are serialized to a real database, not flat player files:
- SQLite: built in, zero setup, perfect for single servers
- MySQL / MariaDB: shared storage for networks
- PostgreSQL: for setups already running Postgres
All database work runs off the main thread on a dedicated executor with a HikariCP connection pool, so saving never blocks the server tick.
Migration
Already have players with vanilla ender chest data? EnhancedEchest imports it automatically on join (when enabled), or on demand with /ee migrate run <player> / all. Each player is migrated only once.
Bedrock support (Geyser)
Menus are built on Paper's modern Dialog API, which Geyser automatically converts into native Bedrock forms (buttons, inputs, and all) with no extra configuration on your side.
Localization
All player-facing text lives in editable language files with full MiniMessage formatting. Ship a translation by copying the en_US folder, translating it, and pointing language at your locale.
Commands
Player
| Command | Description |
|---|---|
/ec |
Open your main chest, or the management menu if you have several and no main set |
/ec #<index> / /ec <name> |
Open one specific chest directly |
/eclist |
Always open the management menu (open, rename, set-as-main per chest) |
Admin (/ee)
| Command | Description |
|---|---|
/ee add <player> <size> [count] [duration] |
Give a player chest(s), optionally temporary |
/ee resize <player> <index> <size> |
Change a chest's slot count (overflow spills safely) |
/ee delete <player> <count> [force] |
Delete a player's newest chests (first chest is always kept) |
/ee view <player> [list | index] |
Open another player's chest: view-only or editable |
/ee migrate run <player> | all |
Import vanilla ender chest data |
/ee reload |
Reload config and language files |
Requirements
| Requirement | Specification |
|---|---|
| Minecraft | 26.1.x only |
| Server | Paper, Folia, Purpur, or compatible Paper forks |
| Java | Java 25+ |
Installation: stop your server, drop the .jar into plugins/, and start. It runs on SQLite out of the box, no extra setup needed.
EnhancedEchest is completely free and open source. Fork it, build on it, or contribute back. ❤️
Information
| Published on | June 24, 2026 |
|---|---|
| Downloads | 2 |