Updating the plugin

General procedure

Your previous setup will still be compatible with new plugin releases:

• changes to the database structure are automatically performed.
• new parameters are automatically added to the end of your config.yml, gui.yml and lang.yml files.

To update, simply replace your old version of the plugin by the latest one. Replacing Java jars while the server is running is not recommended, you should temporarily stop your server to update your plugins.

To be on the safe side, it is recommended to do a backup of the plugin's files and database before updating, even though loss of data following an update has never been reported so far.

---

Updating to a new major version

When the first digit in the version number changes (for example if you update from 6.4.0 to 7.0.0), you are updating to a new major version.

If that's the case, please start the server once with the last release which matches your current major version. For example, if you're running version 6.4.0 of the plugin, start the server once with version 6.7.2 before moving to 7.0.0 or more recent. If you're coming from an older version, for example 5.3.3, first start the server with version 5.16.0, then again with 6.7.2, before finally moving on to 7.0.0 or more recent. You get the idea. :)

Performing major upgrades in this staged way will ensure that all database changes from older versions are performed.