Gives every player on the server a 54-slot ender chest instead of the vanila default 27
Changed
- New default for
temp-enderchest.expiryis now 7d (was 24h), so temporary overflow chests keep their items for a week before expiring. - New default for
database.autosave-intervalis now 3m (was 5m), narrowing the window of unsaved changes if the server is killed hard. - Both only affect fresh installs — existing
config.ymlfiles keep whatever value they already have. Edit those keys (and/ee reloadforautosave-interval) to adopt the new values.
Added
Optional TLS encryption for remote databases. A new
database.sslsetting encrypts the connection to a remote MySQL, MariaDB, or PostgreSQL server. Off by default; requires a full server restart to change (like the other connection settings). SQLite is unaffected.disable(default) keeps the connection unencrypted.requireencrypts the connection but does not verify the server's certificate or hostname — it stops passive snooping, not an active man-in-the-middle.verify-fullencrypts and verifies the certificate chain and hostname; the database server's CA must be trusted by your Minecraft server's JVM. This is the only mode that defends against a man-in-the-middle.- The Redis connection (
cross-server.redis.ssl) verifies the certificate chain and hostname when enabled, matching databaseverify-full.
Cross-server support. Several servers behind a proxy (Velocity, BungeeCord) can now share one database, so a player's ender chests follow them between servers. Off by default; enable it with the new
cross-server.enabledsetting.- Requires a MySQL, MariaDB, or PostgreSQL database shared by every server, plus a shared Redis server (
cross-server.redis.*). SQLite cannot be shared. - Redis stores no chest data. It only tracks which server currently holds a player's data, so fast server switching can never lose or duplicate items.
- Give each server a unique name with
cross-server.server-id, or leave it empty to generate one automatically at every startup. - If Redis is unreachable at startup, or cross-server is enabled with SQLite, the plugin disables itself instead of running unsafely on the shared database.
- Admin commands that target a player who is online on another server fail with an error: view or edit them on the server they are playing on. Run
/ee importwith only one server of the network online.
- Requires a MySQL, MariaDB, or PostgreSQL database shared by every server, plus a shared Redis server (
Added migration from the
CustomEnderChestplugin. Items keep their custom names, lore, and enchantments.CustomEnderChestgives each player a single ender chest, so it imports into EnhancedEchest's chest #1, the same target vanilla migration uses./ee migrate customenderchestimports every player withCustomEnderChestdata./ee migrate customenderchest <player>imports a single player, online or offline.CustomEnderChestmust be set tostorage.type: ymlbefore migrating; itsh2(default) andmysqlbackends are not read.- Safe to re-run: a player's chest #1 is never overwritten once it already holds items.
Added a second style for the
/eclistchest list. Set the newenderchest.list-menuoption toinventoryfor a plain chest GUI that just lists your chests, where clicking a chest opens it right away, instead of the defaultdialogmenu with the rename, set-main, icon, and sort buttons.- The inventory list shows up to 28 chests. A player who owns more than 28 chests always gets the
dialogmenu instead, whatever this is set to.
- The inventory list shows up to 28 chests. A player who owns more than 28 chests always gets the
Information
| Published on | July 14, 2026 |
|---|---|
| Downloads | 2 |