Update the plugin

Whenever a new version of the plugin is released you will be notified in the console.

Updating is as simple as deleting the old plugin.jar and replacing it with the newly downloaded one.

Certain config files can be kept when updating the plugin. Below is a list of files that can be kept and files that should be deleted when updating the plugin.

info

A new install (deleting all files) of the plugin will always work.

Mod Configs

Mod configs located at plugins\ChallengeSystem\mods can normally be kept when updating the plugin.
Although if any mods fail to load after updating the plugin, try deleting the associated mod config file.

Other configs

config.yml
It is recommended to save the old config.yml before updating the plugin. Afterward, you can compare the old and new config.yml to see if any new settings have been added.
(New Settings will always be noted in the changelog)

health.yml
This file can be kept but should be deleted when any errors related to the health of players occur.

mob-heads.yml
This file can generally be kept.

permissions.yml
This file can generally be kept.

Language Files

Language files are located at plugins\ChallengeSystem\language. With every update new features will be added so the language files will grow. To prevent any issues with messages it is recommended to delete the old language files when updating the plugin.

Modified existing language file or have your own?

Make sure to back it up before updating the plugin. The plugin will tell you when a string is missing in the language file. For example:
ChallengeSystem >> Could not find string for mod.something.name.

This means that the message mod.something.name is missing in the language file.
This way you will be able so search for the new messages in the new language file and add them to your existing language file. For this example this means you should add the following to the language file:

mod:
  something:
    name: 'Something'