Список изменений
Changelogs:
Added:
- Nothing
Fixed:
-
/ec migrate to-fileandto-dbmoved nothing. The guide said to run the migration first and switchstorage-typeafterwards. But the migration saved the main chests through the normal save path, which always writes to the storage that is currently active. So: -
to-filewhile still on MySQL wrote every chest back into MySQL. No files were created, the migration still reported success, and after switching tofileall chests looked empty. -
to-dbwhile still on files wrote every chest back into its file and then renamed that file to.data.bak. Nothing reached MySQL.
No items were deleted – they stayed in MySQL (to-file) or in the .data.bak files (to-db).
Now:
- Both migrations read from the source and write straight to the target. The order no longer matters.
- Page names (
/ec rename) and player names are migrated too. - Chests are copied exactly as stored. A chest that can't be read is moved as well and stays recoverable with
/ec repair. to-filekeeps a chest file that already exists as.data.pre-migrationinstead of silently overwriting it.- Broken entries are skipped and listed in the console instead of aborting the whole migration.
- When the migration is done, it tells you what to do next (set
storage-type, restart).
Fix: automatic import on startup could overwrite MySQL data
With storage-type: mysql, the plugin imports leftover .data files on startup. It used to overwrite the MySQL chests with them – for example, going back from file to MySQL replaced the real data with older or empty files.
The automatic import now only adds chests that MySQL doesn't have yet. A file for a chest that already exists in MySQL is renamed to .data.conflict and listed in the console. /ec migrate to-db still replaces on purpose.
Fix: pages 2+ were not saved with MySQL
Pages 2 and up are stored as <uuid>_pageN (42 characters), but the table column only held 36. Depending on the MySQL mode, saving those pages either failed (default on MySQL 8 / MariaDB) or the key was cut to the plain UUID, so the page overwrote the player's main chest.
The column is widened to 64 characters automatically on the first start – nothing to do. The console says Widened the uuid column ... so pages 2+ can be saved once.
Guide
- The migration section now describes the real steps. The setting is called
storage-type(notstorage), and switching needs a restart, not/ec reload.
Affected by the migration bug?
- Stop the server and back up
plugins/EnderChest/and your database. - Went from MySQL to file and the chests are empty: move all
.datafiles out ofplugins/EnderChest/data/(keepplayer_names.yml), install 2.6.4, run/ec migrate to-fileand restart withstorage-type: file. Or simply go back tostorage-type: mysql– the data is still there. - Went from file to MySQL and the chests are empty: rename the
.data.bakfiles inplugins/EnderChest/data/back to.data, install 2.6.4, run/ec migrate to-dband restart withstorage-type: mysql.
Items players put in while the server ran on the wrong storage are in the files you moved away and have to be given back by hand.

