6.8.0

Starting from this release we no longer use data.db to store legacy metadata. It was confusing as users thought it is a SQL database file. We now use legacy-metadata.yml and the file is only made on MC <1.14 when it is called through CompMetadata.

There is no automatic migration due to the sensitive nature of catch-all data.db so plugin authors need to develop one manually (if needed).

Otherwise there are major performance improvements thanks to the legacy metadata file being only saved on server stop/reload instead of every time a metadata is set and one minor GUI security patch.