This release brings a long-asked-for feature, the ability to store player data in SQL databases. Currently SQLite, MySQL and Postgres are supported. I've only tested SQLite so far, though.

SQL Player Data Storage

If you choose to switch how your player data is stored (Yaml files are still the default), please make sure to backup any existing player data first!

Read the documentation carefully, player data can be auto-migrated seamlessly.

If you have a multi-server setup this may work very well for you, there is a locking mechanism that ensures players moving from one server to the other have their data saved and loaded in the correct order to prevent data loss.

In-Game Customization

Configuration files can now be adjusted in-game! In particular this will allow you to easily disable spells, wands or anything else with one quick command.

Please read the documentation linked below if you're interested in this feature, or just type /mconfig in-game (or in the server console) and try it out!

Changelog:

• Add in-game customization commands (/mconfig enable|disable|configure)
  • See: https://github.com/elBukkit/MagicPlugin/wiki/In-Game-Customization
• Add support for storing player data in MySQL, Postgres or SQLite
  • See: https://github.com/elBukkit/MagicPlugin/wiki/Player-Data-Storage
• Fix broken undo for some blocks with extended data
• Fix broom offset problem in MC version 1.12 and below
• Fix sword-based wands having broken icons in 1.12 and below
• Add BattleArena integration, friendly fire flags will respect teams
• Add magic_sp, magic_spell_count, magic_mana and magic_mana_max Placeholders
• More graceful handling of invalid wand icons
• Add "/mage skin" command, which dumps a block of text you can put in a "skin" property of a player disguise
• Add "ironman" mob to survival configs (as an example of using a stored skin)