EnhancedEChest

This release changes how data is stored while the server runs: each player's ender chests are loaded into memory when they join and served from there, so opening and closing chests runs no database queries, no matter which backend you use.

Changed

• Ender chest data is now cached in memory per player. A player's chests are loaded from the database once, when they join, and every operation after that is served from memory. Changes are written back automatically every 5 minutes (new database.autosave-interval setting, minimum 30s, applies on /ee reload), a few seconds after a player quits, and one final time at server shutdown. Memory use stays proportional to the number of online players, not the size of the database.
  • Admin commands on offline players (/ee view, /ee resize, /ee transfer, ...) still work exactly as before: that player's data is loaded on demand and released again after the next autosave.
  • Automatic backups and /ee import always write pending changes first, so they still see complete data.
• Sharing one database between several servers is not supported. Each server holds its own authoritative copy of an online player's data and writes it back on its own schedule, so two servers on the same database (for example behind a proxy with fast server switching) could overwrite each other. Run each server with its own database or SQLite file; cross-server ender chest support will not be available for now.